skills-catalog/ln-780-bootstrap-verifier/SKILL.md
Verifies bootstrapped projects via build, test, and container health checks. Use when validating project setup completeness.
npx skillsauth add levnikolaevich/claude-code-skills ln-780-bootstrap-verifierInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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. Ifshared/is missing, fetch files via WebFetch fromhttps://raw.githubusercontent.com/levnikolaevich/claude-code-skills/master/skills/{path}.
Type: L2 Domain Coordinator Category: 7XX Project Bootstrap Parent: ln-700-project-bootstrap
Orchestrates the final bootstrap verification pipeline by delegating to specialized workers and aggregating results into a comprehensive report.
Scope:
Out of Scope:
| 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 |
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 |
Delegate to ln-781-build-verifier.
Delegate to ln-782-test-runner.
Delegate to ln-783-container-launcher.
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)
| 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}")
| 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 |
../ln-781-build-verifier/SKILL.md../ln-782-test-runner/SKILL.md../ln-783-container-launcher/SKILL.mdMANDATORY 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-10
testing
Drafts and publishes fact-checked GitHub Discussions announcements. Use for releases, updates, or project news; not for release creation or issue responses.
testing
Prepares and publishes a tagged GitHub release from repository evidence. Use for an explicit release request; not for ordinary commits, packages, or community news.
testing
Validates, commits, pushes, and remotely verifies approved repository changes. Use when publication is requested; not for releases, package publishing, or announcements.
development
Reviews standalone skills and their configured distribution surfaces before publication. Use for skill release readiness; not for product code or implementation-plan review.