메뉴
Guide Test-Driven Development using Kent Beck's Red-Green-Refactor cycle. Use when writing tests, implementing features via TDD, or following plan.md test instructions.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Run a PR's full review-fix cycle — wait for review and CI, fix failures, evaluate and reply to comments, then commit and push. Use whenever a PR was just opened or updated — the post-Ship phase of the Orchestrator loop.
Push the current branch and create a pull request with a title and description derived from the commit history. Use when the user asks to open a PR — the Ship step of the Orchestrator loop, always user-triggered.
Delegate a task's implementation wholesale to OpenAI Codex (`codex-run work`) — the whole requirements document in one long autonomous run — keeping policy, orchestration, and acceptance in the main loop. Use at the Implement step of the Orchestrator loop, for any multi-part build.
Cross-model second opinion from OpenAI Codex — `codex-run advise --context` reviews the current session, or pipe a brief. Triggers on "ask codex", "codex review", "second opinion", or the "Cross-model review" rules.
Define requirements before implementation — clarify constraints and design policy, then write a requirements spec and task breakdown for the Implementer to a gitignored plan file. Use at the Plan step of the Orchestrator loop, or whenever a request's scope needs pinning down before building. Never implements; the plan file is its only write.
Root-cause investigation — enumerate competing hypotheses, verify each with evidence, suggest a fix but never apply it. Use when an error, failing test, or anomaly needs diagnosing before any fix is written; implementation hands off to the Implementer.
| name | tdd |
| description | Guide Test-Driven Development using Kent Beck's Red-Green-Refactor cycle. Use when writing tests, implementing features via TDD, or following plan.md test instructions. |
Kent Beck's Red-Green-Refactor cycle with Tidy First principles. This file owns the rules that span the whole cycle; read each phase's detail file as you enter that phase, so the per-phase guidance is in front of you while you act on it.
| Phase | Runs | Does | Detail |
|---|---|---|---|
| RED | once per cycle | Write ONE small failing test | $HOME/.claude/skills/tdd/references/red.md |
| GREEN | once per cycle | Make it pass with minimal code, then commit | $HOME/.claude/skills/tdd/references/green.md |
| REFACTOR | loops | Improve structure with no behavior change, commit each step | $HOME/.claude/skills/tdd/references/refactor.md |
REFACTOR loops until the code is clean; then the next behavior starts a new cycle back at RED.
These hold across every phase — the phase files don't restate them:
feat:/fix: (committed at GREEN); structure is refactor: (committed during REFACTOR). Never mix them in one commit: a reviewer must be able to trust a refactor: touched no behavior.