requesting-code-review

Automate code reviews by dispatching a dedicated subagent to enforce a structured template, categorize feedback by severity, and capture discussions for audit. This streamlines PR lifecycles while maintaining governance and ensuring consistent quality assurance.

The best way to trigger a code review after a subtask is to collect the base and head SHAs, then dispatch the code-reviewer subagent with the implementation details and requirements. This task-aware activation ensures reviews happen exactly when needed.

Ensure consistent and traceable code review feedback by using a template-driven format that categorizes issues by severity and tracks SHAs. This creates an audit trail linking feedback directly to pull requests and deployments for full traceability.

Yes, you can integrate a structured code review workflow into your git lifecycle by dispatching a review agent after major features or before merging to main. It guides reviewers with a consistent process to detect issues early in development.

Before dispatching a code review subagent, you need to collect the base and head SHAs and prepare a review payload containing what was implemented, the plan or requirements, and a brief description of the changes for the template.