requesting-code-review

To request a code review for a specific set of git commits, define the scope using BASE_SHA and HEAD_SHA. This focuses the review on your defined commit range, dispatching a subagent to detect defects and verify changes against stated requirements.

Automating pre-merge code quality checks is best handled by dispatching a code-reviewer subagent with BASE_SHA and HEAD_SHA values. This targets recent changes, classifies severity, and returns triaged findings with recommended actions before code compounds.

Yes, you can review code changes against original project requirements by passing PLAN_OR_REQUIREMENTS alongside the BASE_SHA and HEAD_SHA. The review verifies that implemented changes meet stated requirements and returns severity-triaged findings.

Severity triage for automated code reviews works by classifying detected findings into Critical, Important, or Minor categories. The system then recommends whether to fix the issue immediately, before proceeding, or note it for later.

Yes, you need to provide commit SHA values to review a major feature completion. The review scope is defined by a specific BASE_SHA and HEAD_SHA, ensuring the feedback and defect detection focus strictly on the intended changes.

Using subagent-driven development for per-task code reviews catches defects and contract mismatches early before they compound. Dispatching a subagent with structured placeholders produces focused, actionable feedback specific to the implemented task.