requesting-code-review

You can route code changes to a reviewer after each task by providing the latest task summary and diffs, then prompting a dedicated code-reviewer subagent to review before merging. This enforces plan conformity and base/head diff review.

Automating code reviews before a git merge involves routing changes to a dedicated reviewer subagent after each task. It uses a standardized review template to surface strengths and issues clearly, providing actionable next steps for fixes.

Yes, you can enforce plan conformity during a pull request review by routing base/head diffs to a code-reviewer subagent. It checks task-driven development implementations against the original plan and provides template-driven feedback.

No, this code review workflow does not require specific dependencies. It operates by routing task summaries and diffs to a code-reviewer subagent, making it accessible for typical git workflows without additional setup.

You should use a standardized review template for code reviews to ensure feedback is consistent and audit-ready. It surfaces critical issues clearly and provides actionable next steps for fixes, preventing delayed and inconsistent reviews.

Automated code review routing focuses on task-driven development and pre-merge verification across typical git workflows. It relies on provided task summaries and base/head diffs, meaning it does not review code outside these submitted parameters.