requesting-code-review

To automate code review before a merge, this Skill routes code changes to a dedicated subagent for early quality checks. It dispatches the reviewer automatically after task completion to catch issues sooner in your development workflow.

The best way to trigger early peer review for feature implementations is to describe your completed task and request a review. This initiates the reviewer workflow, applying structured templates and evaluation criteria to guide feedback.

Yes, task-driven development workflows support automated code review subagents. This Skill integrates directly into such workflows, dispatching a reviewer after each task to ensure peer review occurs before merges.

To ensure structured feedback templates are used during a code review, this Skill applies predefined evaluation criteria and categorization rules. It guides the subagent's feedback to maintain consistency across all reviewed changes.

Yes, you can record base and head SHAs for diffs during automated quality assurance checks. The Skill captures these commit references automatically when routing changes to the code-review subagent to ensure accurate diff tracking.

You should avoid automated code review routing for major refactors if your task lacks clear completion criteria or if the changes do not require structured peer review. The Skill is designed for high-stakes updates where early quality checks add value.