requesting-code-review

To automate code reviews before merging a pull request, this Skill dispatches a code-reviewer subagent after task completion using a structured template with Git commit SHAs and implementation details to enforce feedback actions.

The best way to request code reviews in subagent-driven development is to dispatch a focused code-reviewer subagent automatically after each task, applying structured feedback priorities like Critical, Important, and Minor before proceeding to a merge.

A structured code review workflow handles feedback priorities by enforcing specific actions for Critical, Important, and Minor issues identified by the code-reviewer subagent, ensuring major problems are resolved before merging major features.

Yes, you can integrate automated code review requests into your existing Git workflow, as the Skill applies to software projects using Git and dispatches reviews using base and head commit SHAs to analyze recent changes.

To initiate a code review subagent, you need to provide a structured template containing what was implemented, the plan or requirements, base SHA, head SHA, and a description of the changes to be reviewed.

You should dispatch a code-reviewer subagent during the development process immediately after task completion or before merging major features, ensuring issues are caught early and reducing risk before merges.