メニュー
Enforce test-first workflow for bug fixes. Use whenever the user asks to fix a bug, defect, regression, or issue. Write a failing test that captures the bug AND a passing test for the correct behavior BEFORE touching production code, then fix and flip.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | bug-fix-tdd |
| description | Enforce test-first workflow for bug fixes. Use whenever the user asks to fix a bug, defect, regression, or issue. Write a failing test that captures the bug AND a passing test for the correct behavior BEFORE touching production code, then fix and flip. |
When asked to fix a bug/issue/regression, follow this sequence. Do not skip steps.
Add two test cases:
Run the suite. Confirm: bug_case passes, fix_case fails. If this isn't true, you haven't reproduced the bug — stop and re-examine.
Change production code only. Do not edit tests in this step.
Run the suite. Expected result: fix_case passes, bug_case fails.
Now invert bug_case so it asserts the post-fix behavior (i.e. that the broken behavior no longer occurs). The final committed state must have both tests passing and both guarding against regression.
bug_case — flip its assertion so it stays as a regression guard.Run a manual test of the ralph CLI to verify it works end-to-end. Use when you need to smoke test ralph after making changes.
End-to-end ship a feature in this repo — fresh branch from main, local CI gates, commit + push, PR with body, wait for CI, squash-merge, tag at main HEAD, wait for npm publish, verify. Use when the user says "ship this", "release a new version", "create a PR and publish", or describes a code change that should land on npm.
Run CI targets locally, push, and watch remote CI checks. Surfaces issues concisely. All output saved to /tmp.
End-to-end ship a feature in this repo — fresh branch from main, local CI gates, commit + push, PR with body, wait for CI, squash-merge, tag at main HEAD, wait for npm publish, verify. Use when the user says "ship this", "release a new version", "create a PR and publish", or describes a code change that should land on npm.
Run a manual test of the ralph CLI to verify it works end-to-end. Use when you need to smoke test ralph after making changes.