requesting-code-review

You can automate code review initiation by dispatching a focused reviewer subagent with relevant context using a predefined template. This captures implementation details, requirements, base and head SHAs, and descriptions to guide structured assessment.

The best way to trigger a code review before merging is to dispatch a focused reviewer against your HEAD_SHA. This ensures changes are validated against original specifications and conform to quality gates before integration.

A structured code review template improves quality assurance by standardizing the evaluation context with fields like WHAT_WAS_IMPLEMENTED and PLAN_OR_REQUIREMENTS. This guides reviewers to assess actual work against requirements rather than session history.

Yes, you can perform batch reviews of accumulated changes before merging to main. The workflow supports both ad-hoc evaluations after individual tasks and consolidated reviews of major features.

You should avoid automated code review workflows when your changes lack a clear BASE_SHA or HEAD_SHA context. The process relies on predefined templates to compare specific implementations against documented requirements.

Yes, the requesting-code-review subagent works without additional dependencies. It operates by dispatching a reviewer with structured context captured through predefined templates to validate your git workflow changes.