requesting-code-review

To request a code review before merging to main, provide a short description, the plan or requirements, and the base and head git SHAs. This dispatches a reviewer subagent with crafted context to validate your changes and prevent defects.

The best way to automate code review after a feature is to dispatch a dedicated reviewer subagent at right-timing checkpoints. Provide the description, requirements, and git SHAs to evaluate the work product and catch issues before they cascade.

You need a subagent-driven code review when finishing subagent-driven tasks, implementing major features, or preparing to merge to main. These checkpoints ensure changes are validated by a dedicated reviewer before work continues.

Prioritize code review feedback by acting on Critical and Important severity issues immediately. You must fix these prioritized defects before proceeding with your merge or continuing to the next development task.

Dispatching a code reviewer subagent requires the BASE_SHA and HEAD_SHA to define the diff range, plus a DESCRIPTION and PLAN_OR_REQUIREMENTS. This precisely crafted context ensures the reviewer evaluates the work product, not the full session history.

If the code reviewer subagent provides incorrect feedback, the skill guides you on how to respond when the reviewer is wrong. This allows you to dismiss invalid Critical or Important issues and proceed with your merge.