requesting-code-review

To review a git diff against requirements, you provide a description, plan, base SHA, and head SHA to an isolated reviewer agent that generates severity-categorized findings and a clear merge readiness verdict.

Severity triage in code review categorizes findings into Critical, Important, and Minor, directing you to fix Critical issues immediately, resolve Important ones before continuing, and record Minor issues for later.

You need an isolated code review after completing subtasks or major features in subagent-driven development to prevent late-stage regressions by forcing a focused review of changes against the plan before merging.

Yes, you can use base SHA and head SHA values to define a precise git range that isolates the diff for completed changes, ensuring the reviewer agent only evaluates the specific work product against requirements.

The best way to verify code readiness before merging to main is dispatching a requirement-focused reviewer agent with a git diff range to produce a clear merge readiness verdict based on severity-calibrated feedback.