requesting-code-review

Code review identifies issues before merge by dispatching a reviewer subagent with your git changes and implementation plan. Provide base and head SHAs, and the reviewer produces structured feedback on strengths, issues by severity, and production-readiness assessment.

You need git SHAs for both the base commit and head commit representing your changes. The review process uses these to compare implemented work against your plan scope and validate quality before production deployment.

Request review after completing major features, post-task in subagent-driven development, and before merging to main. Mandatory review after each task ensures quality gates are met and prevents issues from cascading into production.

Code review produces structured feedback covering identified strengths, issues categorized by severity level, and a production-readiness assessment that indicates whether changes are safe to merge.

Yes. By comparing base and head SHAs, the review examines all implemented changes within your plan scope, ensuring comprehensive coverage of modifications before they reach production.