Menú
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
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.
Use when doing any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when you have a written implementation plan to execute with review checkpoints
Use when implementation is complete and all tests pass — guides completion by presenting structured options for merge, PR, or cleanup
Use when receiving code review feedback, before implementing suggestions — requires technical rigor and verification, not performative agreement
Use when starting feature work that needs isolation from current workspace or before executing implementation plans
Basado en la clasificación ocupacional SOC
| name | nobody-requests-code-review |
| description | Use when completing tasks, implementing major features, or before merging to verify work meets requirements |
Before declaring work complete or merging, run a structured self-review or delegate to the reviewer subagent.
Announce at start: "I'm using the requesting-code-review skill to verify this work."
Before requesting review, verify:
git diff main...HEAD (or appropriate base)Use the reviewer subagent for an independent perspective:
/review <scope of changes>
Or via the subagent tool directly:
Use reviewer agent to review: <description of what changed>
| Level | Action | Example |
|---|---|---|
| Critical | Must fix before merge | Security hole, data loss, crash |
| Warning | Should fix | Missing validation, poor error message |
| Suggestion | Consider | Better naming, minor refactor |