ln-780-bootstrap-verifier
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chineseln-780-bootstrap-verifier
ln-780-bootstrap-verifier
Type: L2 Domain Coordinator
Category: 7XX Project Bootstrap
Parent: ln-700-project-bootstrap
类型: L2 域协调器
分类: 7XX 项目引导
父级: 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 |
| 场景 | 是否使用该Skill |
|---|---|
| ln-700完成项目设置后 | 是 |
| 独立构建验证 | 否，直接使用ln-781 |
| 仅手动测试 | 否，直接使用ln-782 |
| 仅容器启动 | 否，直接使用ln-783 |
Workflow
工作流
Phase 1: Pre-flight Checks
阶段1: 预检检查
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 |
在启动验证流水线前，验证环境就绪状态。
| 检查项 | 检测方式 | 失败处理动作 |
|---|---|---|
| Docker已安装 | 检查docker命令是否可用 | 报告错误，跳过容器阶段 |
| Docker Compose | 检查docker compose版本 | 报告错误，跳过容器阶段 |
| 项目结构 | 扫描package.json、*.csproj、docker-compose.yml文件 | 根据检测到的组件调整工作流 |
| 端口可用性 | 检查所需端口是否空闲 | 向用户发出警告，建议替代方案 |
Phase 2: Build Verification
阶段2: 构建验证
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)
委派给 ln-781-build-verifier 处理。
- 传递检测到的项目类型
- 收集构建结果（状态、耗时、输出路径）
- 失败时：收集错误日志，继续生成报告（跳过测试/容器阶段）
Phase 3: Test Verification
阶段3: 测试验证
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
委派给 ln-782-test-runner 处理。
- 传递构建结果作为上下文信息
- 收集测试结果（总用例数、通过数、失败数、耗时）
- 失败时：收集失败详情，可选择继续执行容器阶段
Phase 4: Container Launch
阶段4: 容器启动
Delegate to ln-783-container-launcher.
- Pass project configuration
- Collect container status and health check results
- On failure: collect container logs
委派给 ln-783-container-launcher 处理。
- 传递项目配置信息
- 收集容器状态及健康检查结果
- 失败时：收集容器日志
Phase 5: Report Generation
阶段5: 报告生成
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 |
将所有结果汇总为最终验证报告。
报告章节:
| 章节 | 内容 |
|---|---|
| 构建结果 | 各项目的状态、耗时、输出路径 |
| 测试结果 | 各测试套件的总用例数、通过数、失败数 |
| 容器状态 | 各容器的名称、状态、端口、健康状态 |
| 健康检查 | 各端点的URL、状态码、响应时间 |
| 后续步骤 | 提供给用户的可操作建议 |
Worker Invocation
工作组件调用
Use Skill tool to delegate work:
| Worker | Invocation | Data Passed |
|---|---|---|
| ln-781-build-verifier | | Detected project types |
| ln-782-test-runner | | Build status, skip flag |
| ln-783-container-launcher | | Compose file path |
Sequential execution required: Build -> Test -> Container
使用Skill工具委派任务：
| 工作组件 | 调用方式 | 传递数据 |
|---|---|---|
| ln-781-build-verifier | | 检测到的项目类型 |
| ln-782-test-runner | | 构建状态、跳过标记 |
| ln-783-container-launcher | | Compose文件路径 |
需按顺序执行: 构建 -> 测试 -> 容器
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 |
| 选项 | 默认值 | 描述 |
|---|---|---|
| runTests | true | 执行测试阶段 |
| skipTestsOnFailure | false | 测试失败时是否继续执行容器阶段 |
| startContainers | true | 执行容器阶段 |
| keepContainersRunning | true | 验证完成后保持容器运行状态 |
| healthCheckTimeout | 120 | 等待容器健康的最长秒数 |
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
- 所有检测到的项目类型均构建成功
- 所有测试套件已执行（若启用）
- 所有容器状态健康（若启用）
- 已生成验证报告并展示给用户
- 已提供后续步骤建议
版本: 2.0.0
最后更新: 2026-01-10