requesting-code-review

Automate code review before a git merge by dispatching a code-reviewer subagent to evaluate recent changes. The subagent checks plan alignment and provides a documented rationale for acceptance or rejection decisions.

Automated code review requires a clear description of what was implemented, the plan or requirements, and the starting and ending git SHAs to compare. This ensures the reviewer can verify progress and alignment accurately.

Trigger a code review at key milestones like feature completions, before critical releases, or prior to merging. This ensures a fresh assessment of code changes to catch issues early and reduce defects.

Code review works with subagent-driven development workflows by coordinating a formal code-reviewer subagent. It evaluates recent changes before merge to maintain project quality and reduce defects.

Check if implemented work matches the original plan by using git SHAs to verify progress. The code reviewer compares the starting and ending SHAs against the defined requirements to ensure alignment.

A subagent for code review relies on receiving a clear implementation description and accurate git SHAs. Without these precise inputs, the automated reviewer cannot effectively evaluate changes or provide reliable readiness feedback.