requesting-code-review

Automate code review by dispatching a code-reviewer subagent after task completion to catch issues early. This applies to development tasks, major feature implementations, and pre-merge checks across plan execution to ensure quality before rollout.

Yes, you can run an iterative review loop. The automated code review process supports a review, fix, and re-review loop until all issues are resolved, utilizing retries and timeouts for reliable decision making.

The best way to perform pre-merge code checks is dispatching a code-reviewer subagent. It standardizes feedback and evidence collection, ensuring structured quality assurance and reducing rework and risk before rollout.

Automated code review triggers after task completion or during major feature milestones. You initiate it by dispatching the code-reviewer with a description and plan references for the latest commit in your branch.

Evidence-backed reporting in code review works by standardizing feedback collection during the subagent dispatch. It provides operational guidance that ensures reliable decision making throughout the iterative review and fix loop.