requesting-code-review

You can automate pre-merge code reviews by dispatching a dedicated code-reviewer subagent to verify new work and deliver structured feedback before merging to main. This workflow requires collecting implementation details, requirements, base and head SHAs, and a description.

A subagent code review workflow dispatches a dedicated reviewer to verify new work, reducing defects and rework. It enforces reviews after each task or major feature and before merging to main, ensuring alignment with project requirements.

To request a code review after completing a task, dispatch the code-reviewer subagent and share the implementation details. You need to provide what was implemented, plan or requirements, base SHA, head SHA, and a description.

You need a formal code review before merging to main across collaborative projects, after completing tasks ranging from small fixes to major features. This enforcement verifies and stabilizes code changes, reducing defects and rework.

Yes, dispatching a code reviewer works for tasks ranging from small fixes to major features. The workflow applies consistently across collaborative projects to catch issues early, maintain quality, and ensure alignment with requirements before merging.

You need to provide what was implemented, the plan or requirements, the base SHA, the head SHA, and a description. Collecting these details allows the code-reviewer subagent to deliver structured feedback and guide next steps.