requesting-code-review

A pre-merge code review evaluates completed work against requirements using a scoped git commit range to catch regressions before changes reach the main branch. It provides structured reviewer context and severity-based triage for clear merge readiness.

To request a code review, define the git commit range using BASE_SHA and HEAD_SHA, then provide a DESCRIPTION and PLAN_OR_REQUIREMENTS to scope the review to the actual diffs. This ensures feedback is grounded in the specific changes made.

Severity-based triage categorizes review feedback into Critical, Important, and Minor issues to drive clear next steps. This model dictates whether to fix immediately, fix before proceeding, or note for later to ensure merge readiness.

Yes, subagent-driven development supports early, frequent review prompts after each subagent task and major feature completion. This approach ensures newly completed work is evaluated against requirements before cascading issues or merging.

A code reviewer needs four structured context fields: DESCRIPTION, PLAN_OR_REQUIREMENTS, BASE_SHA, and HEAD_SHA. This brief ensures the review focuses strictly on the work product and actual git diffs rather than session history.