requesting-code-review

A pre-merge code review dispatches a reviewer subagent using a diff range, plan, and description to validate implementation against requirements before merging, preventing defect propagation.

Pre-merge code review is needed after each subagent task completion or major feature implementation to checkpoint changes against explicit requirements before they cascade into further work.

Dispatching a code reviewer requires providing a description, plan or requirements text, and the base and head SHAs to scope the git diff evaluation and keep feedback grounded.

Severity-categorized feedback separates issues into Critical, Important, and Minor, providing actionable guidance on whether to fix immediately, note for later, or push back with reasoning.

Yes, the subagent code review uses a tight diff-based context scoped to a specific BASE_SHA to HEAD_SHA range rather than the whole session history, keeping the evaluation focused.

Dispatch a dedicated code-reviewer subagent with the feature description, plan, and specific git diff range to evaluate the implementation against explicit requirements and receive categorized feedback.