メニュー
Create structural guard tests that enforce architecture principles on every `make quality` run. Guards are AST-scanning tests that prevent categories of violations automatically. Available guards: schema-inheritance, boundary-completeness, query-type-safety, no-error-dicts.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Start an isolated PostgreSQL container for integration testing. Each worktree gets its own container on a unique port — no mutex, no conflicts. Use this before running integration tests in a worktree agent.
Two-pass BDD step assertion completeness inspector. Pass 1 (Sonnet): triage all Then steps — FLAG or PASS. Pass 2 (Opus): deep trace flagged steps with full production context, producing architectural judgment on what the correct assertion should be. Use after writing or modifying BDD step definitions to catch assertion mismatches (steps that claim to verify X but actually only check existence).
Derive obligation tests using the test harness. First checks for harness availability, then generates compact tests using domain-specific test environments. Hard gate: no harness -> no tests (stops immediately). Replaces obligation-test for harness-enabled domains.
Run a repeatable code review audit on migration changes. Inventories files by architectural layer, reviews each layer against #1050/#1066 principles, and files beads issues for findings. Re-run after remediation batches to track progress.
Derive integration tests from existing unit test xfails and UNSPECIFIED stubs. Uses integration-from-stub formula: catalog → review → triage → architect → write-integration → fix-green → reconcile-xfail → verify → commit. Each stub's expected behavior is the core invariant. Architect atom reads 7 architecture docs and cross-references against CRIT-1..CRIT-11 findings.
Map the complete test surface for domain entities by cross-referencing test-obligations with existing tests. Produces one canonical test module per entity with real tests + skip stubs for gaps. Every obligation maps to exactly one test. Run this before /remediate.
| name | guard |
| description | Create structural guard tests that enforce architecture principles on every `make quality` run. Guards are AST-scanning tests that prevent categories of violations automatically. Available guards: schema-inheritance, boundary-completeness, query-type-safety, no-error-dicts. |
| args | <guard-name-1> [guard-name-2] ... |
Create AST-scanning enforcement tests that catch architecture violations
automatically. Each guard runs on make quality and prevents regressions.
/guard <guard-name-1> [guard-name-2] ...
Guard names (space-separated). Each gets a test file at
tests/unit/test_architecture_{guard_name}.py.
| Guard | What It Enforces |
|---|---|
| schema-inheritance | Schema classes extend correct adcp library base types |
| boundary-completeness | MCP/A2A/REST wrappers expose all _impl parameters |
| query-type-safety | DB queries use column types matching the column definition |
| no-error-dicts | _impl functions raise exceptions, never return error dicts |
Custom guard names are also supported — the research atom will determine what to enforce based on the name and #1050/#1066 principles.
These already exist (don't recreate):
test_no_toolerror_in_impl.py — No ToolError in _impl functionstest_transport_agnostic_impl.py — No transport imports in _impltest_impl_resolved_identity.py — _impl accepts ResolvedIdentitypython3 .claude/scripts/cook_formula.py \
--formula .claude/formulas/structural-guard.yaml \
--var "GUARD_NAMES={all_args}" \
--epic-title "Guards: {all_args}"
Dry run first (recommended):
python3 .claude/scripts/cook_formula.py \
--formula .claude/formulas/structural-guard.yaml \
--var "GUARD_NAMES={all_args}" \
--epic-title "Guards: {all_args}" \
--dry-run
bd ready → bd show <atom-id> → execute → bd close <atom-id> → repeat
Each guard goes through: research → scan → write-guard → mark-known → verify → commit.
All guards committed and passing in make quality.
/surface — Create entity test suites (what the guards protect)/remediate — Fill entity test stubs (fix the violations guards find)/mol-execute — Execute individual beads tasks