requesting-code-review

Automated code review for recent git changes uses a subagent-driven workflow to validate your base and head SHA diff range, checking requirement mismatches and returning an explicit merge readiness assessment before changes land in main.

Requirement validation is performed by providing the implementation details and original plan requirements to a code-reviewer subagent, which compares them against the git diff to return categorized issues and actionable resolution guidance.

Code review should be requested after each completed task in subagent-driven development, after major feature work, before merging to main, when stuck, or before refactoring to prevent architecture drift and bugs from compounding.

Dispatch the code-reviewer subagent by providing what was implemented, the plan requirements, a git base and head SHA range, and a description so the reviewer can run diff-based checks and assess merge readiness.

A git base and head SHA range is required for the code review workflow to function, as it scopes the review context so the subagent can inspect exactly what changed and return accurate strengths and categorized issues.

An early code review loop prevents bugs, architecture drift, and requirement mismatches by categorizing findings by severity and telling you what to fix immediately versus later before changes land in main.