requesting-code-review

Automating code review requests requires dispatching the code-reviewer subagent with your BASE_SHA and HEAD_SHA to catch issues early and prevent cascading defects. This enforces mandatory peer validation after each task completion.

A pre-merge code review workflow is needed for major feature completion and before merging to main. It validates changes after completing tasks in subagent-driven development to prevent cascading defects from progressing downstream.

Running an automated pull request review requires capturing the BASE_SHA starting commit, HEAD_SHA current commit, a brief summary of implemented changes, and a reference to the task plan or requirements before dispatching the code-reviewer subagent.

The code-reviewer subagent structures pull request feedback using a standardized template at code-reviewer.md, categorizing issues into Critical, Important, and Minor severity levels for acting on feedback before proceeding with merges.

This code review automation works without external dependencies, relying solely on dispatching the code-reviewer subagent and providing commit SHAs to enforce quality assurance in subagent-driven development workflows.