ln-781-build-verifier
Scannednpx machina-cli add skill levnikolaevich/claude-code-skills/ln-781-build-verifier --openclawPaths: 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.
ln-781-build-verifier
Type: L3 Worker Category: 7XX Project Bootstrap Parent: ln-780-bootstrap-verifier
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 |
|---|---|
| Called by ln-780 orchestrator | 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
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
Source
git clone https://github.com/levnikolaevich/claude-code-skills/blob/master/ln-781-build-verifier/SKILL.mdView on GitHub Overview
The ln-781-build-verifier automatically detects project types from repository markers, restores dependencies, runs builds, and confirms artifacts exist. It supports common ecosystems (Node.js, .NET, Python, Go, Rust, Java) and ensures every detected project compiles before proceeding.
How This Skill Works
It scans the repository root for type markers (e.g., package.json, *.csproj, go.mod, etc.), then uses the appropriate package manager and build tool to restore dependencies and compile in Release/Production mode. After building, it verifies the presence of expected artifacts (dist/build, bin/Release, binaries) and returns a structured result including projectName, projectType, status, duration, outputPath, and errorMessage if any.
When to Use It
- Called by ln-780 orchestrator
- Standalone build verification
- CI/CD pipeline build step
- Pre-release validation
- Pre-merge quality checks
Quick Start
- Step 1: Run the verifier at the repo root to auto-detect projects
- Step 2: Let it restore dependencies and build all detected projects
- Step 3: Review the returned results (projectName, status, outputPath) for success
Best Practices
- Always restore dependencies before building to avoid flaky failures
- Build in production/release mode to surface real issues
- Verify that artifacts exist and are accessible after each build
- Report results for every project, including failures
- Detect all project types before attempting builds
Example Use Cases
- A monorepo containing Node.js, .NET, and Go projects is auto-detected and built in one pass
- A CI job runs ln-781-build-verifier to validate a fresh clone before deployment
- Standalone verification of a newly-added Python package and its dependencies
- Cross-language projects in a monorepo are built and artifacts collected for release
- Post-clone validation in a multi-service repo ensuring all builds succeed
