requesting-code-review

Automated code reviews in a subagent workflow route changes to a dedicated subagent for evaluation. This ensures consistent feedback after tasks or before merging, preserving developer context while surfacing issues promptly.

A structured code review requires a template containing what was implemented, the plan or requirements, and the base and head git SHAs. Providing this precise context improves the evaluation quality and formal feedback output.

Trigger a code review subagent after completing each task, finishing major features, and before merging to main. This captures timely feedback and enforces review discipline at critical points in the development workflow.

Automated code review feedback follows a formal structure detailing strengths, identified issues, and actionable recommendations. This standardized output ensures consistent quality assurance evaluation across development tasks.

Integrate code quality assurance by dispatching a code-reviewer subagent directly into your development process. This enforces review discipline with standardized prompts, generating structured feedback without disrupting your workflow.

Automated code review requires a structured template to function correctly. Without providing the implementation details, plan, and git SHAs, the subagent cannot generate the expected formal review with strengths, issues, and recommendations.