Menú
Drive implementation through red-green-refactor with isolated test design, minimal implementation, and behavior-preserving cleanup.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Route an independent review-only agent to a stronger model tier or reasoning effort at key decision points, then continue the task in the main agent. Use when the user asks for an adviser, advisor, second opinion, stronger review, or Claude Code /advisor-like behavior; before committing to a consequential approach on a multi-step task; when work is stuck or changing direction; and before declaring substantial work complete.
Monitor or resume GitHub pull requests, fix CI failures and actionable CodeRabbit, Codex, bot, or human review feedback, push focused updates, and stop only when the PR is merge-ready or has a concrete external blocker.
Convert review feedback, CI failures, bug fixes, or task retrospectives into a durable project feedback ledger, then make future implementation work consult that ledger before planning.
Run an end-to-end implementation delivery workflow from user request to merge-ready pull request. Use when the user asks Codex to implement a change and expects planning, goal tracking, UI design where relevant, code edits, tests, self-review, regular ready-for-review PR creation, CI/review follow-up, and bringing the PR as close to mergeable as possible.
Analyze recent Codex work and package repeated patterns as the smallest useful skill, custom subagent, hook, or automation. Use when asked to mine sessions, memories, or recent repeated work for reusable Codex assets.
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
| name | tdd |
| description | Drive implementation through red-green-refactor with isolated test design, minimal implementation, and behavior-preserving cleanup. |
Use this workflow when the user wants new behavior developed under TDD discipline, or when a risky behavior change benefits from a failing test before implementation.
When subagents are available, keep phases isolated: pass the behavior only to a test-writing subagent, pass the failing test only to an implementation subagent, and pass the green code only to a refactoring subagent.
Include:
