Review code changes for quality, security, and correctness. Use when the user says "review this PR", "review these changes", "check my code", "look at what I changed", or after implementing a feature. Produces a severity-organized report.
Produce a severity-organized review report covering security, correctness, and quality for code changes.
Identify issues in code changes, organized by severity (Critical > Warnings > Suggestions), with specific file:line references and fix suggestions for every finding. Done when the report is presented to the user.
Before reviewing, read CLAUDE.md and any linter/formatter config files (.eslintrc, pyproject.toml, .prettierrc, etc.) to understand project conventions. Do not flag style issues already handled by configured tooling.
$ARGUMENTS specifies a file, branch, or PR: use that scope$ARGUMENTS is empty: run git diff main...HEAD. If that returns nothing, ask: "What should I review — a branch, specific files, or uncommitted changes?"CHECKPOINT: Present the identified files and diff scope. Confirm this is the correct review target before proceeding.
Critical (must fix before merge):
Warnings (should fix):
Suggestions (nice to have):
For each finding:
path/to/file.ts:42Organize findings by severity: Critical first, then Warnings, then Suggestions.
Report is presented inline in the conversation, organized by severity. Offer to save to .claude/memory/review-YYYY-MM-DD.md if the user wants a record.