requesting-code-review

To perform a git commit range code review, provide a reviewer subagent with BASE_SHA and HEAD_SHA references. The subagent evaluates code quality, architecture, and tests against plan requirements, returning categorized issues with file:line references and concrete fixes.

Checklist-driven code review evaluates git diffs against plan requirements to assess code quality, architecture, and testing. You need this process before merging major feature branches, after completing subagent tasks, or when stuck to catch regressions early and maintain implementation alignment.

Yes, you can request a targeted pull request code review in subagent-driven development by dispatching a reviewer subagent. Send the BASE_SHA, HEAD_SHA, implementation summary, and plan reference to receive an independent, categorized assessment with actionable fixes before merging.

The best way to ensure code quality before merging a major feature branch is dispatching a structured review request. Provide the BASE_SHA, HEAD_SHA, and implementation summary to a reviewer subagent to compare changes against plan requirements and categorize issues by severity with actionable fixes.

Yes, providing a plan reference is required to get actionable code review feedback. The reviewer subagent uses the stated plan requirements to compare against your BASE_SHA..HEAD_SHA diffs, ensuring the evaluation checks for adherence to the original implementation plan and categorizes issues accurately.

Code review feedback lacks specific file and line references when the reviewer subagent is not dispatched with the correct BASE_SHA and HEAD_SHA commit range. Providing the exact git diff range ensures the evaluation categorizes issues by severity with precise file:line references for production readiness.