requesting-code-review

To request a code review before merging, provide the agent with Git SHAs, an implementation summary, and plan context so it can dispatch a focused reviewer to catch regressions in your React Native workflow.

Subagent-driven development routes completed tasks through a dedicated reviewer agent to maintain quality. Peer review fits in by validating each task batch before issues propagate into the main implementation plan.

You get severity-based feedback by routing git commits through a code reviewer that categorizes findings into Critical, Important, and Minor, ensuring you know which fixes are urgent before proceeding.

You should request a peer review after completing task batches, finishing major feature builds, or before merges to keep your implementation plan intact and catch regressions early.

An implementation plan is required context for the reviewer. The workflow depends on providing plan references alongside Git SHAs and implementation summaries to ensure mission-focused feedback.