requesting-code-review

To get an actionable code review before merging, dispatch a code-reviewer subagent with the Base SHA, Head SHA, and a brief description to analyze diffs, categorize issues by severity, and return a ready-to-merge verdict.

To review code changes between two git commits, provide the BASE_SHA and HEAD_SHA references to evaluate the diff against requirements, checking code quality, architecture, and testing coverage.

Verifying code quality in subagent-driven development involves requesting a checklist-driven assessment after each completed task to evaluate implementation correctness, architecture, and production readiness.

Yes, you can use a code review checklist to categorize issues by severity, assessing code quality, architecture, testing, and requirements alignment to produce structured, actionable feedback.

You need a pre-merge code review for major feature completions to ensure changes are evaluated for correctness, architecture, tests, and production readiness before causing regressions or reaching the main branch.

Yes, the code review process provides a clear ready-to-merge verdict by analyzing diffs between two git SHAs and categorizing issues by severity to determine production readiness.