home / skills / levnikolaevich / claude-code-skills / ln-780-bootstrap-verifier

ln-780-bootstrap-verifier skill

/ln-780-bootstrap-verifier

This skill coordinates final bootstrap verification by delegating build, test, and container checks to specialized workers and compiling a unified report.

npx playbooks add skill levnikolaevich/claude-code-skills --skill ln-780-bootstrap-verifier

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
4.5 KB
---
name: ln-780-bootstrap-verifier
description: Orchestrates final verification - build, test, and container health checks
---

> **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.

# 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

1. **Never execute builds/tests/containers directly** - always delegate to workers
2. **Fail-fast on build errors** - skip test and container phases
3. **Always generate report** - even on failure, include collected data
4. **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

Overview

This skill orchestrates the final bootstrap verification pipeline by coordinating build, test, and container health checks and then producing a consolidated verification report. It delegates actual work to specialized worker skills and focuses on sequencing, aggregation, and actionable outcomes. Use it after initial project bootstrap to validate readiness for next delivery steps.

How this skill works

The verifier runs pre-flight environment checks, then sequentially invokes the build, test, and container worker skills according to detected project types and configuration options. It collects structured results from each worker (status, durations, logs, health checks) and applies fail-fast rules for build failures while optionally continuing on test failures. Finally, it aggregates findings into a human-friendly report with per-phase results and recommended next steps.

When to use it

  • Immediately after ln-700 project bootstrap to validate build, test, and container readiness
  • When you need a single verification pass that aggregates multiple worker outputs
  • Before merging or deploying a newly bootstrapped project to confirm baseline health
  • When you want a consistent, repeatable verification report across projects
  • When you need to leave containers running after verification for manual inspection

Best practices

  • Run pre-flight checks in the same environment where subsequent stages will run to catch local issues early
  • Enable runTests by default; set skipTestsOnFailure only when container validation is higher priority
  • Keep keepContainersRunning true when you expect manual debugging after failures
  • Collect and preserve worker logs and artifacts for triage; always attach them to the final report
  • Follow the fail-fast rule for builds to avoid wasting time on downstream phases if compilation fails

Example use cases

  • Validate a freshly generated multi-language project (Node, .NET) to ensure all builds succeed
  • Run CI pipeline step that aggregates build, test, and container health results into one report
  • Smoke-test containerized services after bootstrap and leave containers alive for manual troubleshooting
  • Generate actionable next steps for developers after an automated verification run
  • Quality gate in a PR workflow that must fail fast on build errors but continue to collect diagnostics

FAQ

Does this skill run builds or tests directly?

No. It delegates to specialized worker skills for builds, tests, and containers and only orchestrates and aggregates results.

What happens if the build fails?

The verifier applies fail-fast: it skips tests and containers for that run but still generates a full report including build errors and logs.