requesting-code-review

A code review for uncommitted git changes evaluates your working directory by collecting git status and diff outputs, populating a review template, and routing it to a subagent to catch defects before merging to main.

Validating code quality after a major feature involves requesting a focused code review that uses git diff scopes to verify requirements and prioritize Critical, Important, or Minor issues before they cascade into additional work.

Yes, you can review a specific committed range. The code review process supports committed range, uncommitted work, or mixed work scopes, ensuring the reviewer subagent inspects only the exact changes relevant to merge safety.

You need a focused code review in subagent-driven development after completing tasks, finishing major features, or before merging to main. This timing catches defects early and keeps progress safe before issues compound into additional work.

Yes, git diff based code review works without extra dependencies. It relies on standard git status and diff commands to collect reviewable facts, populates a built-in code-reviewer template, and routes the evaluation to a subagent.

Using a subagent for code review provides an evidence-driven evaluation with a fresh perspective. It maps your git diff to a structured template, prioritizes actionable feedback by severity, and guides what to fix next to prevent cascading issues.