requesting-code-review

Get the base and head git SHAs with git rev-parse, then dispatch a general-purpose subagent using the code-reviewer.md template. Fill in the description, requirements, and SHA placeholders, and the reviewer returns categorized issues with a merge verdict.

Request review after each task in subagent-driven development, after completing a major feature, and before merging to main. It is also valuable when stuck on a problem, before refactoring, or after fixing a complex bug.

The reviewer checks plan alignment, code quality, architecture decisions, test coverage, and production readiness including migrations and backward compatibility. It categorizes findings as Critical, Important, or Minor with file:line references.

Push back with technical reasoning rather than accepting incorrect feedback. Show code or tests that prove the implementation works, and request clarification on the reviewer's concern.

The reviewer receives only precisely crafted context — the description, requirements, and git diff range — never your session history. This keeps the reviewer focused on the work product rather than your thought process and preserves your own context.