requesting-code-review

Get the base and head git SHAs for your change range, then dispatch a general-purpose subagent using the code-reviewer.md template. Fill in the description, requirements, and SHA placeholders so the reviewer evaluates only the relevant diff.

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

The reviewer checks plan alignment, code quality, architecture, testing, and production readiness. It returns strengths, issues categorized as Critical, Important, or Minor, recommendations, and a clear merge readiness verdict.

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

Providing BASE_SHA and HEAD_SHA keeps the reviewer focused on the actual work product via git diff, not your thought process. This preserves your own context and gives the reviewer precisely scoped, unbiased input.