Menu
Required TDD loop for tasks that need red, green, refactor, final-green, and test-quality evidence.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Instructions for using gcode CLI for code search and retrieval. Loaded on demand when project has a code index.
Pre-transition checklist for closing or reviewing tasks. Covers fresh verification evidence, commits, and memory gates.
Use when processing CodeRabbit review comments, CodeRabbit CLI reports, or `$gobby coderabbit [findings]` requests.
Use when creating, editing, or validating Gobby skills, especially when a skill must change agent behavior or become discoverable through gobby-skills.
Use when coordinating a full gobby build run for an epic or task, especially when the user assigns the current session as coordinator, asks for a coordination epic, wants build agents/worktrees monitored, or wants gobby build bugs fixed so future runs work unattended.
Router contract for provider-aware Gobby help and installed skill dispatch.
| name | test-driven-development |
| description | Required TDD loop for tasks that need red, green, refactor, final-green, and test-quality evidence. |
| version | 1.0.0 |
| category | core |
| triggers | tdd, test-driven development, red green refactor |
| metadata | {"gobby":{"audience":"agent","depth":1}} |
Use this when a task requires TDD.
The task handoff must include:
When tests were added or heavily edited, run:
uv run gobby test-quality audit <paths> --baseline .gobby/test-quality-baseline.json --fail-on-new --min-severity high
TDD is not satisfied by writing tests after implementation, by only running a broad suite, or by omitting the expected red failure.