Menú
Rigorous code review covering correctness, security (OWASP Top 10), and quality.
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
Ensure this skill is active before every journal write — new entry, edit, restructure, or activity log append. Provides the graph protocol (bidirectional links, indexes), the directory layout, and the activity log format that keep the journal consistent.
Activate when the turn's deliverable is source, test, code analysis, or config files — editing or creating code. Provides the Research → Strategy → Execution workflow, the complexity budget, and specialised deep-dive companions (testing, debug, refactor, review).
Activate when the turn's deliverable is a design — system architecture, API contract, data model, component decomposition, or trade-off analysis. Provides the Constraints → Explore → Decide → Specify → Plan workflow for sound, well-reasoned designs.
Activate when the turn's deliverable is findings, comparisons, recommendations, or an investigation-backed plan — answering questions, analyzing unfamiliar code, exploring new domains. Provides the systematic Scope → Discover → Synthesize → Plan workflow.
Activate when the turn's deliverable is substantial prose — docs, copy, proposals, feedback, commit/PR text, or UI strings. Provides copywriting frameworks, tone guidance, and editing workflow for clear, persuasive, polished output.
Force explicit research mode — Scope → Discover → Synthesize → Plan — with the approval gate before any implementation.
| name | review |
| description | Rigorous code review covering correctness, security (OWASP Top 10), and quality. |
| user-invocable | true |
| disable-model-invocation | true |
The user invoked /review with: $ARGUMENTS
Procedure:
core-coding is activated for this session. If you can't recall its companion layout from earlier, re-activate via ActivateSkill('core-coding') — silent and auto-approved.core-coding's companion files, locate the review methodology guide and Read it.git diff HEAD against changed files in the current working tree.code-reviewer agent per the instruction in the review guide rather than reviewing inline.file_path:line, verdict).