requesting-code-review

Code review requests capture your base and head Git SHAs, dispatch a code-reviewer subagent with structured details, and return categorized feedback on strengths and issues. Provide commit references and requirements to trigger automated review before merge.

Early code review feedback prevents issues from compounding later in the cycle, reducing technical debt and production risk. Requesting reviews after major features and before merging ensures quality gates are applied consistently.

Issues are categorized as Critical, Important, or Minor to help you prioritize fixes by impact. This structure surfaces blockers first and clarifies which problems must be resolved before merging.

Code review requests integrate into pull request workflows by automating review dispatch after each task or major feature. They capture Git SHAs and requirements, then return structured feedback for production readiness assessment.

Provide base and head Git SHAs, a description of changes, and clear requirements or context. The code-reviewer subagent uses this structured input to perform thorough review and return categorized feedback.

Early review catches issues while they're isolated and cheaper to fix, preventing cascading problems and rework. Delaying reviews compounds technical debt and increases risk to production stability.