Ln 781 Build Verifier
Builds all detected projects and verifies successful compilation. Use when checking that a bootstrapped project compiles.
MCP get_skill({ skillId: "ln-781-build-verifier-867d304a" })Use this skill with your agent
Create a free account and connect via MCP
> **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
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
---
**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-10Related Skills
More skills in Software Engineering
Accessibility Standards
Comprehensive web accessibility standards based on WCAG 2.2 AA, with 38+ anti-patterns, legal enforcement context (EAA, ADA Title II), WAI-ARIA patterns, and framework-specific fixes for modern web frameworks and libraries.
Accord
Authoring unified specification packages across Business/Development/Design teams via staged elaboration (L0 Vision → L1 Requirements → L2 Team Detail → L3 Acceptance Criteria). No code. Use when authoring cross-team specs, building L0-L3 packages, or aligning Biz/Dev/Design on a single source of truth.
Acquire Codebase Knowledge
Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.
Acreadiness Assess
Run the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wraps `npx github:microsoft/agentrc readiness` and hands off rendering to the @ai-readiness-reporter custom agent. Supports policies (--policy) for org-specific scoring. Use when asked to assess, audit, or score the AI readiness of a repo.
Acreadiness Generate Instructions
Generate tailored AI agent instruction files via AgentRC instructions command. Produces .github/copilot-instructions.md (default, recommended for Copilot in VS Code) plus optional per-area .instructions.md files with applyTo globs for monorepos. Use after running /acreadiness-assess to close gaps in the AI Tooling pillar.
Acreadiness Policy
Help the user pick, write, or apply an AgentRC policy. Policies customise readiness scoring by disabling irrelevant checks, overriding impact/level, setting pass-rate thresholds, or chaining org baselines with team overrides. Use when the user asks about strict mode, AI-only scoring, custom weights, CI gating, or wants org-wide standardisation.
Explore Other Categories
Skills from other categories with shared topics
Ln 014 Agent Instructions Manager
Creates AGENTS.md canonical and CLAUDE.md @AGENTS.md stub; audits token budget, cache safety, import-pattern compliance. Use when instruction files need alignment.
Ln 022 Researchgraph
Indexes and queries project research graphs backed by hex-research MCP. Use for hypotheses, goals, benchmark runs, evidence depth, derived goal metrics, lineage, generated research maps, and graph audits.
Ln 100 Documents Pipeline
Creates complete project documentation system (project docs, reference, tasks, tests). Use when bootstrapping docs from scratch or regenerating all.