requesting-code-review

Automating code review requests involves dispatching a code-reviewer subagent after task completion to catch issues before merging. This workflow uses structured templates with diff and base/head SHA placeholders to standardize feedback capture for production readiness.

To initiate a code-review workflow, you need a review template, placeholders for the diff, and the base/head SHAs. Providing these inputs ensures the automated reviewer subagent can properly track branch changes and store structured feedback for production gating.

You should trigger an automated code review after completing a task, finishing major feature work, or preparing major changes across branches. This ensures formal validation and structured feedback are captured before any code progresses toward production deployment.

Yes, automated code review applies to major changes across branches by tracking the diff alongside base and head SHAs. This validates feature work and captures feedback to gate progress and ensure production readiness before merging.

The best way to standardize feedback capture is using structured review templates with placeholders for diffs and base/head SHAs. This guides the code-reviewer subagent to consistently document issues and store feedback to gate production readiness.

Automating code review dispatch requires predefined templates and correct base/head SHAs to function properly. It standardizes feedback gating for production readiness but depends on accurate diff placeholders to validate major changes across branches effectively.