requesting-code-review

Get the base and head commit 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 so the reviewer evaluates the exact diff range.

Request a review after every completed task in subagent-driven development, after finishing significant features, and before merging to main. It is also valuable when stuck, before refactoring, or after fixing complex bugs.

The reviewer returns strengths, issues classified as Critical, Important, or Minor with file and line references, improvement suggestions, and a final assessment stating whether the work can be merged, needs fixes first, or should not merge.

No. Provide only carefully organized context: a description of the changes, the plan or requirements, and the git SHA range. This keeps the reviewer focused on the work product rather than your reasoning process.

Push back with technical reasoning, show code or tests proving the approach works, and ask for clarification. Never ignore Critical issues or continue with unfixed Important issues, but legitimate technical disagreement is acceptable.