ln-781-build-verifier
Builds all detected projects and verifies successful compilation. Use when checking that a bootstrapped project compiles.
- Installs
- 381
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-781-build-verifier- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads ln-781-build-verifier automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Paths: File paths (
references/,../ln-*) are relative to this skill directory.
MANDATORY READ: Load references/ci_tool_detection.md — build command registry, exit-code preservation, and compact output rules.
ln-781-build-verifier
Type: L3 Worker Category: 7XX Project Bootstrap
Purpose
Detects project types, restores dependencies, executes builds, and verifies successful compilation.
Scope:
- Auto-detect project types from file markers
- Restore dependencies using appropriate package manager
- Execute build commands for each project
- Verify build artifacts exist
Out of Scope:
- Running tests (handled by ln-782)
- Container operations (handled by ln-783)
- Workflow orchestration (handled by ln-780)
When to Use
| Scenario | Use This Skill |
|---|---|
| Standalone-capable | Yes |
| Standalone build verification | Yes |
| CI/CD pipeline build step | Yes |
| Test execution needed | No, use ln-782 |
Workflow
Step 1: Detect Project Types
Scan project root for type markers.
| Marker File | Project Type | Build System |
|---|---|---|
| package.json | Node.js/Frontend | npm/yarn/pnpm |
| *.csproj | .NET | dotnet |
| setup.py / pyproject.toml | Python | pip/poetry |
| go.mod | Go | go build |
| Cargo.toml | Rust | cargo |
| pom.xml | Java/Maven | mvn |
| build.gradle | Java/Gradle | gradle |
Step 2: Restore Dependencies
For each detected project, restore dependencies before building.
| Project Type | Dependency Restoration |
|---|---|
| Node.js | Install packages from lock file |
| .NET | Restore NuGet packages |
| Python | Install from requirements or pyproject |
| Go | Download modules |
| Rust | Fetch crates |
Step 3: Build Projects
Execute build for each project type in Release/Production mode.
| Project Type | Build Mode | Expected Outcome |
|---|---|---|
| Node.js | Production | Bundled assets in dist/ or build/ |
| .NET | Release | Compiled DLLs in bin/Release/ |
| Python | Editable install | Package installed in environment |
| Go | Production | Compiled binary |
| Rust | Release | Optimized binary in target/release/ |
Step 4: Verify Build Artifacts
Confirm build outputs exist.
| Project Type | Artifact Check |
|---|---|
| Node.js | dist/ or build/ directory exists, contains files |
| .NET | DLL files in bin/Release/{framework}/ |
| Python | Package importable |
| Go | Binary executable exists |
| Rust | Binary in target/release/ |
Step 5: Report Results
Return structured results to orchestrator.
Result Structure:
| Field | Description |
|---|---|
| projectName | Name of the project |
| projectType | Detected type (nodejs, dotnet, python, etc.) |
| status | success / failed |
| duration | Build time in seconds |
| outputPath | Path to build artifacts |
| errorMessage | Error details if failed |
Error Handling
| Error Type | Recovery Action |
|---|---|
| Dependency restore failed | Check network, verify lock file integrity |
| Compilation errors | Log full error output, report as failed |
| Missing build tool | Report required tool installation |
| Timeout | Report timeout, suggest increasing limit |
Critical Rules
- Always restore dependencies first - builds may fail without fresh dependencies
- Use production/release mode - development builds may hide issues
- Verify artifacts exist - successful exit code is not sufficient
- Report all projects - include both successful and failed builds
Monitor (2.1.98+): For build/restore commands expected >30s, use Monitor. Fallback: Bash(run_in_background=true).
Definition of Done
- All project types detected
- Dependencies restored for each project
- Build executed for each project
- Artifacts verified to exist
- Results returned to orchestrator
Reference Files
- Parent:
../ln-780-bootstrap-verifier/SKILL.md
Version: 2.0.0 Last Updated: 2026-01-10
FAQ
What does the ln-781-build-verifier skill do?
Builds all detected projects and verifies successful compilation. Use when checking that a bootstrapped project compiles.
How do I install ln-781-build-verifier?
Run npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-781-build-verifier in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/ln-781-build-verifier/ (personal) or .claude/skills/ln-781-build-verifier/ (project).
Which AI agents can use ln-781-build-verifier?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is ln-781-build-verifier safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains ln-781-build-verifier?
It is published by levnikolaevich in levnikolaevich/claude-code-skills. It has 381 recorded installs.
More from levnikolaevich/claude-code-skills
ln-100-documents-pipeline
levnikolaevich/claude-code-skills
Creates complete project documentation system (project docs, reference, tasks, tests). Use when bootstrapping docs from scratch or regenerating all.
ln-620-codebase-auditor
levnikolaevich/claude-code-skills
Open the skill to read its SKILL.md instructions.
ln-775-api-docs-generator
levnikolaevich/claude-code-skills
Configures Swagger/OpenAPI documentation for backend APIs. Use when adding interactive API docs to a project.
ln-624-code-quality-auditor
levnikolaevich/claude-code-skills
Open the skill to read its SKILL.md instructions.
ln-782-test-runner
levnikolaevich/claude-code-skills
Executes all test suites and reports results with coverage. Use when verifying that test infrastructure works after bootstrap.
ln-634-test-coverage-auditor
levnikolaevich/claude-code-skills
Open the skill to read its SKILL.md instructions.
Popular other skills
hyperframes-cli
heygen-com/hyperframes
The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.
triage
mattpocock/skills
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
ask-matt
mattpocock/skills
Ask which skill or flow fits your situation. A router over the skills in this repo.
to-questionnaire
mattpocock/skills
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
loop-me
mattpocock/skills
Grill me about specs for the workflows I want to build, within this workspace.