Overview

This skill dispatches a code-reviewer agent to catch issues before they cascade. The core principle is to review early and review often, especially after completing tasks, implementing major features, or before merging to main.

How This Skill Works

The system retrieves the base and head git SHAs, dispatches the code-reviewer agent with the relevant task context, and then acts on the feedback. It prioritizes fixes by severity: Critical fixes must be applied immediately, Important fixes before proceeding, and Minor notes are recorded for later.

When to Use It

• After each task in subagent-driven development
• After completing major features
• Before merge to main
• When verifying that work meets requirements before handoff
• During CI/CD or release prep to guard the main branch

Quick Start

1. Step 1: Get base and head SHAs from the git history.
2. Step 2: Dispatch the code-reviewer agent with the task context and plans.
3. Step 3: Act on feedback by applying Critical fixes immediately, Important fixes before proceeding, and noting Minor items for later.

Best Practices

• Always fetch the correct base and head SHAs before requesting a review
• Provide full task context and relevant plans when dispatching the reviewer
• Act on feedback promptly, prioritizing Critical fixes immediately
• Address Important fixes before proceeding with the next steps
• Document Minor notes for future improvements and iterate with subsequent reviews

Example Use Cases

• A subagent completes a feature; SHAs are retrieved, and the code-reviewer is dispatched to catch design or security issues before integrating.
• A major feature is finished; a review is requested to surface potential edge cases and performance concerns.
• Before merging a feature branch to main, a formal code review is conducted and critical blockers are fixed first.
• Review returns minor notes; developers log the items for later improvements while proceeding with essential tasks.
• During subagent-driven development, the code-reviewer is regularly invoked to maintain quality and prevent cascading defects.

Frequently Asked Questions