Menu
Review a code change for correctness, security, contracts, and tests.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
| name | review |
| description | Review a code change for correctness, security, contracts, and tests. |
| user-invocable | true |
| argument-hint | [optional: file path, diff, commit, or focus area] |
Find the change from $ARGUMENTS or the conversation. Ask if unclear. If REVIEW.md exists at the repo root, follow it. Flag pre-existing problems only if the change reaches or worsens them. Do not fix anything.
Review to disprove, not confirm. Treat confident prose as non-evidence; verify behavior from code and tests.
Check task behavior, edge cases, failure paths, security boundaries, contracts, and existing patterns. Check whether tests prove changed behavior. Flag dead code left by the change: unused variables, compatibility shims with no consumers, and comments narrating removed code.
Flag new dependencies when the project already has a way to do the same thing, hand-rolled code covered by the standard library or platform, abstractions with one implementation, config nobody sets, and wrappers that only delegate.
For complexity findings, name what to cut and what replaces it: existing helper, standard library function, platform feature, simpler local code, or nothing.
List findings: blockers, important, then nits. For each finding, include location, severity, bug, impact, and fix direction when it changes the next action.
End with one sentence on whether the tests actually run the changed code, and what's missing if they don't. Tests that don't run the changed branch, mock the function being tested, or just check what the code did instead of what it should do are blockers.
Break a spec, brief, issue tracker item, or user request into agent-sized tasks, using phases and milestones only when they clarify larger work, delivered to exactly one destination.
Bootstrap a new or empty project repository with a local skeleton: README, license, .gitignore, AGENTS.md, docs, and optional commit or push only when explicit. Interview the repo creator when file-changing decisions are unclear.
Create a traceable Git branch for the current task.
Verify browser-rendered work in a real browser. Use for HTML, UI, visual docs, presentations, local apps, and browser-facing changes.
Stage intended changes and create one Conventional Commit.
Find and fix the root cause when something breaks: a failing test, a broken build, a bug report, or behavior that doesn't match expectations. Use when the user says 'debug', 'why is this failing', 'fix this bug', or when a failure interrupts other work.
