メニュー
Infrastructure artifact verification: Docker builds, CI workflows, and launcher flags must be executed, not just syntax-checked.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Multi-agent delegation rules, three-phase workflow (Plan/Build/Review), model selection, collaboration gates, and Ralph Loop integration.
Autonomous build driver after SDD spec approval: phase-scoped headless build sessions, driver-owned commits, cross-provider review gates, milestone pauses, and fail-closed escalation — under explicit opt-in autonomy profiles.
When and how to ask clarifying questions before implementing. Data model review gate and ambiguity resolution rules.
Quality gates, prohibited patterns, verification discipline, and self-audit rules for all code generation and review sessions.
Cross-copilot portable conventions: read before write, minimal changes, git discipline, project structure, and priority rules.
Copyright header rules for generated source files. Applies the company name from providers.toml to new files.
| name | infra-verification |
| description | Infrastructure artifact verification: Docker builds, CI workflows, and launcher flags must be executed, not just syntax-checked. |
Any artifact whose correctness cannot be verified by a language-level test runner MUST be executed before committing. This includes: Dockerfiles, docker-compose files, shell scripts, CI workflows, launcher scripts, and hook scripts.
| Artifact | Minimum Verification | Full Verification |
|---|---|---|
| Dockerfile | docker build -t verify . | Build + run + healthcheck |
| docker-compose.yml | docker compose config | docker compose up --build -d + healthcheck + down |
.sh script | bash -n script.sh | Run with --help or --dry-run if supported |
.github/workflows/*.yml | actionlint (if available) | YAML schema validation |
| Launcher flags | Run <launcher> --help | Run with new flag and verify output |
When infrastructure verification fails, distinguish:
Docker healthchecks MUST use dedicated health endpoints (/actuator/health, /healthz,
/health), not business endpoints. Business endpoints may require auth, have side effects,
or return errors unrelated to service health.
Demo/example endpoints MUST return meaningful sample data, not empty stubs ([], null, {}).
Verify each endpoint with a test request and confirm the response is non-empty and
structurally correct.
When the project uses a terminal multiplexer (detected via claude-code, $TMUX, or $CMUX_WORKSPACE_ID):
If you write a manual test plan with executable commands:
