ln-780-bootstrap-verifier

Original🇺🇸 English
Translated

Orchestrates final verification - build, test, and container health checks

2installs
Added on

NPX Install

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

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

ScenarioUse This Skill
After ln-700 completes project setupYes
Standalone build verificationNo, use ln-781 directly
Manual testing onlyNo, use ln-782 directly
Container-only launchNo, use ln-783 directly

Workflow

Phase 1: Pre-flight Checks

Verify environment readiness before starting verification pipeline.
CheckDetection MethodFailure Action
Docker installedCheck docker command availabilityReport error, skip container phase
Docker ComposeCheck docker compose versionReport error, skip container phase
Project structureScan for package.json, *.csproj, docker-compose.ymlAdapt workflow to detected components
Port availabilityCheck if required ports are freeWarn 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:
SectionContent
Build ResultsStatus, duration, output paths per project
Test ResultsTotal, passed, failed counts per suite
Container StatusName, status, port, health per container
Health ChecksURL, status code, response time per endpoint
Next StepsActionable items for user

Worker Invocation

Use Skill tool to delegate work:
WorkerInvocationData 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

OptionDefaultDescription
runTeststrueExecute test phase
skipTestsOnFailurefalseContinue to container phase if tests fail
startContainerstrueExecute container phase
keepContainersRunningtrueLeave containers running after verification
healthCheckTimeout120Max 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

Version: 2.0.0 Last Updated: 2026-01-10