菜单
Read-only review verifying that an acceptance test mirrors its Gherkin scenario in structure, semantics, and intent. Returns a verdict OK or REGENERATE. Invoked by red-cycle, also callable standalone on any test/scenario pair.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Fetch bot and human review comments on the current PR, apply every actionable change in scope, commit and push. Used by pr-auto-merge inside the ATDD pipeline. Can also be invoked standalone via /apply-pr-feedback or /apply-pr-feedback <pr-number>.
End-to-end ATDD pipeline. Use when the user wants to take a user story from impact mapping all the way to merged code, or types /atdd-run.
Watch a sub-PR through bot review + CI, run /apply-pr-feedback on actionable feedback, then auto-merge into its base branch. Refuses to act when base is the trunk (main/master). Use after green-cycle opens a draft PR, or when the user types /auto-merge <pr-number>.
Generate Gherkin acceptance scenarios from a context.md, with mandatory interview for ambiguities, concrete data, and test-level tags. Use after impact-map, or when the user provides a user story and rules and asks for scenarios.
First-run configuration for the atdd-pipeline plugin in the current project. Picks an issue tracker, spec base path, commit style, and writes .atdd-pipeline.json at the repo root. Idempotent. Use after installing the plugin in a new repo.
ATDD GREEN phase. Generate the minimal implementation that makes the RED test pass, run review-architecture and review-intent in parallel, auto-correct up to 2 times, then escalate. Use after red-cycle on the same scenario branch, or when the user types /green <issue-number>.
| name | review-fidelity |
| description | Read-only review verifying that an acceptance test mirrors its Gherkin scenario in structure, semantics, and intent. Returns a verdict OK or REGENERATE. Invoked by red-cycle, also callable standalone on any test/scenario pair. |
| phase | review |
| parallel | false |
| inputs | ["scenario-text","test-file"] |
| outputs | ["fidelity-report","verdict"] |
| escalation | none |
Test-fidelity reviewer for Phase 4a. Read-only critique of a single test against the Gherkin scenario it claims to implement.
red-cycle after a test is generated./review-fidelity <test-file> <scenario-file> to audit existing tests against their specs.scenario-text — the Scenario: block from the .feature file (or the issue body).test-file — the test source file.Produce a markdown report with three sections, then a verdict line.
Given / When / Then.Then clauses.Given step is realized as setup; not skipped, not merged.Flag with STRUCTURE: <line> — <issue>.
Flag with SEMANTICS: <expected> vs <actual>.
expect(true).toBe(true), assert(...) of a tautology, missing Then mapping).Flag with INTENT: <test location> — <issue>.
Last line: VERDICT: OK (no flags) or VERDICT: REGENERATE (any flag).