菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
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.
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.
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.
基于 SOC 职业分类
| name | surface |
| description | 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. |
| args | <entity-name-1> [entity-name-2] ... |
Create canonical test suites per domain entity by mapping all test obligations to real tests or stubs. This gives complete visibility into what's tested and what's missing.
/surface <entity-name-1> [entity-name-2] ...
Entity names (space-separated). Each gets a test file at
tests/unit/test_{entity_name}.py (hyphens → underscores).
| Entity | Primary Obligations | Output File |
|---|---|---|
| product | UC-001 | test_product.py |
| media-buy | UC-002, UC-003 | test_media_buy.py |
| delivery | UC-004 | test_delivery.py |
| creative-formats | UC-005 | test_creative_formats.py |
| creative | BR-UC-006 | test_creative.py |
| properties | BR-UC-007 | test_properties.py |
| audience-signals | BR-UC-008 | test_audience_signals.py |
| performance | BR-UC-009 | test_performance.py |
| capabilities | BR-UC-010 | test_capabilities.py |
| pricing-option | business-rules, constraints | test_pricing_option.py |
| transport-boundary | #1050/#1066 principles | test_transport_boundary.py |
All entities also check cross-cutting files: business-rules.md, constraints.md.
For each entity, a test module containing:
@pytest.mark.skip(reason="STUB: [obligation-ID]") for every gapOpen test_creative.py → see 89 test names → 30 real, 59 stubs → know exactly what's missing.
python3 .claude/scripts/cook_formula.py \
--formula .claude/formulas/entity-test-surface.yaml \
--var "ENTITY_NAMES={all_args}" \
--epic-title "Surface: {all_args}"
Dry run first (recommended):
python3 .claude/scripts/cook_formula.py \
--formula .claude/formulas/entity-test-surface.yaml \
--var "ENTITY_NAMES={all_args}" \
--epic-title "Surface: {all_args}" \
--dry-run
bd ready → bd show <atom-id> → execute → bd close <atom-id> → repeat
Each entity goes through: gather-obligations → audit-existing → review → triage → generate-suite → verify → commit.
All entity suites committed. Coverage summary generated.
Test names describe behavior, not bugs:
test_create_media_buy_rejects_missing_brand (behavior)test_bug_fix_123 or test_v2_compat (incident-driven)/remediate — Fill the stubs this skill creates/guard — Structural guards that prevent new violations/mol-execute — Execute individual beads tasks (now entity-suite-aware)