ln-781-build-verifier
Builds all detected projects and verifies successful compilation. Use when checking that a bootstrapped project compiles.
Best use case
ln-781-build-verifier is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Builds all detected projects and verifies successful compilation. Use when checking that a bootstrapped project compiles.
Teams using ln-781-build-verifier should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ln-781-build-verifier/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ln-781-build-verifier Compares
| Feature / Agent | ln-781-build-verifier | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Builds all detected projects and verifies successful compilation. Use when checking that a bootstrapped project compiles.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
> **Paths:** File paths (`shared/`, `references/`, `../ln-*`) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root. If `shared/` is missing, fetch files via WebFetch from `https://raw.githubusercontent.com/levnikolaevich/claude-code-skills/master/skills/{path}`.
# 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
1. **Always restore dependencies first** - builds may fail without fresh dependencies
2. **Use production/release mode** - development builds may hide issues
3. **Verify artifacts exist** - successful exit code is not sufficient
4. **Report all projects** - include both successful and failed builds
---
## 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-10Related Skills
ln-780-bootstrap-verifier
Verifies bootstrapped projects via build, test, and container health checks. Use when validating project setup completeness.
ln-622-build-auditor
Checks compiler/linter errors, deprecation warnings, type errors, failed tests, build config issues. Use when auditing build health.
ln-914-community-responder
Responds to unanswered GitHub discussions and issues with codebase-informed replies. Use when clearing community question backlog.
ln-913-community-debater
Launches RFC and debate discussions on GitHub. Use when proposing changes that need community input or voting.
ln-912-community-announcer
Composes and publishes announcements to GitHub Discussions. Use when sharing releases, updates, or news with the community.
ln-911-github-triager
Produces prioritized triage report from open GitHub issues, PRs, and discussions. Use when reviewing community backlog.
ln-910-community-engagement
Analyzes community health and delegates engagement tasks. Use when managing GitHub issues, discussions, and announcements.
ln-840-benchmark-compare
Runs built-in vs hex-line benchmark with scenario manifests, activation checks, and diff-based correctness. Use when measuring hex-line MCP performance against built-in tools.
ln-832-bundle-optimizer
Reduces JS/TS bundle size via tree-shaking, code splitting, and unused dependency removal. Use when optimizing frontend bundle size.
ln-831-oss-replacer
Replaces custom modules with OSS packages using atomic keep/discard testing. Use when migrating custom code to established libraries.
ln-830-code-modernization-coordinator
Modernizes codebase via OSS replacement and bundle optimization. Use when acting on audit findings to reduce custom code.
ln-823-pip-upgrader
Upgrades Python pip/poetry/pipenv dependencies with breaking change handling. Use when updating Python dependencies.