ln-780-bootstrap-verifier
Scannednpx machina-cli add skill levnikolaevich/claude-code-skills/ln-780-bootstrap-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-780-bootstrap-verifier
Type: L2 Domain Coordinator Category: 7XX Project Bootstrap Parent: ln-700-project-bootstrap
Purpose
Orchestrates the final bootstrap verification pipeline by delegating to specialized workers and aggregating results into a comprehensive report.
Scope:
- Coordinates build, test, and container verification
- Aggregates results from all workers
- Generates final verification report
Out of Scope:
- Direct execution of builds/tests/containers (delegated to workers)
- Project structure creation (handled by earlier phases)
When to Use
| Scenario | Use This Skill |
|---|---|
| After ln-700 completes project setup | Yes |
| Standalone build verification | No, use ln-781 directly |
| Manual testing only | No, use ln-782 directly |
| Container-only launch | No, use ln-783 directly |
Workflow
Phase 1: Pre-flight Checks
Verify environment readiness before starting verification pipeline.
| Check | Detection Method | Failure Action |
|---|---|---|
| Docker installed | Check docker command availability | Report error, skip container phase |
| Docker Compose | Check docker compose version | Report error, skip container phase |
| Project structure | Scan for package.json, *.csproj, docker-compose.yml | Adapt workflow to detected components |
| Port availability | Check if required ports are free | Warn user, suggest alternatives |
Phase 2: Build Verification
Delegate to ln-781-build-verifier.
- Pass detected project types
- Collect build results (status, duration, output paths)
- On failure: collect error logs, proceed to report (skip test/container phases)
Phase 3: Test Verification
Delegate to ln-782-test-runner.
- Pass build results for context
- Collect test results (total, passed, failed, duration)
- On failure: collect failure details, optionally continue to container phase
Phase 4: Container Launch
Delegate to ln-783-container-launcher.
- Pass project configuration
- Collect container status and health check results
- On failure: collect container logs
Phase 5: Report Generation
Aggregate all results into final verification report.
Report Sections:
| Section | Content |
|---|---|
| Build Results | Status, duration, output paths per project |
| Test Results | Total, passed, failed counts per suite |
| Container Status | Name, status, port, health per container |
| Health Checks | URL, status code, response time per endpoint |
| Next Steps | Actionable items for user |
Worker Invocation
Use Skill tool to delegate work:
| Worker | Invocation | Data Passed |
|---|---|---|
| ln-781-build-verifier | Skill: ln-781-build-verifier | Detected project types |
| ln-782-test-runner | Skill: ln-782-test-runner | Build status, skip flag |
| ln-783-container-launcher | Skill: ln-783-container-launcher | Compose file path |
Sequential execution required: Build -> Test -> Container
Critical Rules
- Never execute builds/tests/containers directly - always delegate to workers
- Fail-fast on build errors - skip test and container phases
- Always generate report - even on failure, include collected data
- Pre-flight checks first - detect environment issues before starting
Options
| Option | Default | Description |
|---|---|---|
| runTests | true | Execute test phase |
| skipTestsOnFailure | false | Continue to container phase if tests fail |
| startContainers | true | Execute container phase |
| keepContainersRunning | true | Leave containers running after verification |
| healthCheckTimeout | 120 | Max seconds to wait for healthy containers |
Definition of Done
- All detected project types built successfully
- All test suites executed (if enabled)
- All containers healthy (if enabled)
- Verification report generated and displayed to user
- Next steps provided
Reference Files
- Worker:
../ln-781-build-verifier/SKILL.md - Worker:
../ln-782-test-runner/SKILL.md - Worker:
../ln-783-container-launcher/SKILL.md
Version: 2.0.0 Last Updated: 2026-01-10
Source
git clone https://github.com/levnikolaevich/claude-code-skills/blob/master/ln-780-bootstrap-verifier/SKILL.mdView on GitHub Overview
ln-780-bootstrap-verifier coordinates the final bootstrap verification by delegating work to specialized workers and aggregating results into a single report. It verifies build readiness, runs tests, and checks container health, then compiles a comprehensive status overview. This role ensures traceable, end-to-end visibility before handoff.
How This Skill Works
As a coordinator, it runs pre-flight environment checks, then sequentially delegates to ln-781-build-verifier, ln-782-test-runner, and ln-783-container-launcher. It aggregates per-project results (status, duration, outputs) and health data into a final report, including sections for Build, Test, Container Status, and Health Checks.
When to Use It
- After ln-700 completes project setup
- Standalone build verification
- Manual testing only
- Container-only launch
- End-to-end verification in CI or staging
Quick Start
- Step 1: Run pre-flight environment checks (Docker availability, docker-compose, project structure, ports).
- Step 2: Delegate to ln-781-build-verifier, then to ln-782-test-runner, and finally to ln-783-container-launcher; collect results.
- Step 3: Generate and review the final verification report, ensuring Build, Test, Container, Health, and Next Steps sections are populated.
Best Practices
- Never execute builds/tests/containers directly; delegate to workers
- Fail-fast on build errors; skip test and container phases
- Always generate a final report; include collected data even on failure
- Perform pre-flight environment checks first to detect issues
- Keep per-project results auditable with time stamps and output paths
Example Use Cases
- In a CI/CD pipeline, ln-780 coordinates builds via ln-781, tests via ln-782, and containers via ln-783, producing a consolidated final report.
- When a build fails, the verifier captures error logs and still generates the report with partial data for remediation.
- If tests fail but containers report healthy status, the final report includes health data and actionable Next Steps.
- Pre-flight checks identify missing Docker or port conflicts before initiating verification.
- The final report’s sections (Build Results, Test Results, Container Status, Health Checks, Next Steps) guide release decisions.
