requesting-code-review

Pre-merge code review against specific requirements is performed by dispatching a reviewer subagent with a scoped context, a git diff range, and your plan to evaluate changes. The review yields severity-based issue classifications and a clear merge readiness verdict.

Requirement validation in a git diff code review is the process of evaluating code changes against explicit acceptance criteria to prevent requirement drift. It categorizes findings by severity and provides evidence-backed feedback before merging.

You can review code changes without session history by dispatching a dedicated reviewer subagent with tightly scoped context. This subagent evaluates the work product independently using only the provided description, requirements, and git diff range.

To get a ready to merge verdict after completing a major feature, request a code review by providing the task description, plan, and git diff range. The reviewer assesses the changes and returns a concrete recommendation on merge readiness.

The best way to classify code review findings by severity is to use an automated reviewer subagent that categorizes issues as Critical, Important, or Minor. This ensures actionability and provides evidence-backed feedback for each finding.

You need a subagent-driven development checkpoint for code review when you want to prevent bugs and quality issues from compounding before moving on. It ensures changes get evaluated against the plan and acceptance criteria early.