requesting-code-review

To automate a formal code review before merging, use the /request-review command to dispatch a dedicated code-reviewer subagent that verifies your latest changes against specs and coding standards. This structured feedback process ensures early issue detection.

A subagent code review workflow routes your completed task to a dedicated reviewer agent to verify compliance with specs and edge-case handling. You need it after completing tasks, implementing major features, or before merging to reduce regression risks.

To ensure traceability when requesting a code review, the dispatched subagent documents the process using a standardized template that records base and head SHAs. This provides a formal record of structured feedback for your pull request.

Yes, you can use an automated code review workflow for major feature implementations. By dispatching a code-reviewer subagent, you enforce a quality gate that checks for compliance with coding standards and potential edge cases before merging.

Initiating a code review with a subagent does not require any external dependencies or components. It operates independently to prompt pre-review steps and assign a reviewer to verify your changes using a standardized template.