requesting-code-review

To automate code-review requests before merging, you can dispatch a code-reviewer subagent after completing tasks or major features. This enforces git SHA capture and standardized templates to guide structured feedback and maintain production readiness.

You should trigger a peer review in subagent-driven workflows after completing each task, finishing major features, or before merging to main. Optional triggers include when you are stuck or preparing to refactor code.

Git SHAs and templates standardize the code review process by capturing exact commit states and enforcing structured feedback. This guides reviewers consistently, ensuring quality assurance and early issue detection across all automation workflows.

Yes, this code review automation works without external dependencies. It relies entirely on dispatching a code-reviewer subagent within your existing workflows, using native git SHAs and standardized templates to capture and review code changes.

The best way to ensure production readiness with early code reviews is to enforce mandatory subagent-driven checks after each task. Using standardized templates and structured feedback catches issues early before merging to main.