ln-780-bootstrap-verifier
Verifies bootstrapped projects via build, test, and container health checks. Use when validating project setup completeness.
Best use case
ln-780-bootstrap-verifier is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Verifies bootstrapped projects via build, test, and container health checks. Use when validating project setup completeness.
Teams using ln-780-bootstrap-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-780-bootstrap-verifier/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ln-780-bootstrap-verifier Compares
| Feature / Agent | ln-780-bootstrap-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?
Verifies bootstrapped projects via build, test, and container health checks. Use when validating project setup completeness.
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-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 |
---
**TodoWrite format (mandatory):**
```
- Pre-flight checks (in_progress)
- Invoke ln-781-build-verifier (pending)
- Invoke ln-782-test-runner (pending)
- Invoke ln-783-container-launcher (pending)
- Generate verification report (pending)
```
## Worker Invocation (MANDATORY)
| Phase | Worker | Context |
|-------|--------|---------|
| 2 | ln-781-build-verifier | Shared (Skill tool) — build verification for detected project types |
| 3 | ln-782-test-runner | Shared (Skill tool) — test suite execution |
| 4 | ln-783-container-launcher | Shared (Skill tool) — container launch + health checks |
**All workers:** Invoke via Skill tool — workers see coordinator context.
**Sequential execution required:** Build -> Test -> Container
**Invocations:**
```
Skill(skill: "ln-781-build-verifier", args: "{detected_project_types}")
Skill(skill: "ln-782-test-runner", args: "{build_status}")
Skill(skill: "ln-783-container-launcher", args: "{compose_file_path}")
```
---
## 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`
---
## Meta-Analysis
**MANDATORY READ:** Load `shared/references/meta_analysis_protocol.md`
Skill type: `review-coordinator — workers only`. Run after all phases complete. Output to chat using the `review-coordinator — workers only` format.
---
**Version:** 2.0.0
**Last Updated:** 2026-01-10Related Skills
ln-781-build-verifier
Builds all detected projects and verifies successful compilation. Use when checking that a bootstrapped project compiles.
ln-700-project-bootstrap
Bootstraps projects to production-ready structure. Use when creating new or transforming existing projects.
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.