How does this skill identify which code to review?

It uses Git commands to identify specific SHAs (Base and Head), allowing the reviewer subagent to focus exactly on the changes made between the starting point and the current state.

When is the best time to trigger a code review?

Reviewing early and often is recommended. Specifically, you should trigger a review after every sub-task in a development plan and always before merging a feature into your main branch.

Does this work with subagent-driven development?

Yes, it is specifically designed to act as a quality gate in subagent workflows, catching issues at each step before they compound in later tasks.

How should I handle feedback from the AI reviewer?

Address 'Critical' and 'Important' issues immediately. For 'Minor' issues, you can note them for later. If the reviewer is technically incorrect, you are encouraged to push back with reasoning and evidence.

Automated Code Reviewer

Name: Automated Code Reviewer
Author: dazeb

bydazeb

•

Collaboration Tools

Orchestrates structured code reviews using specialized subagents to catch bugs and architectural issues before they are merged.

About

The Requesting Code Review skill establishes a rigorous quality control framework for Claude Code workflows. By utilizing Git SHAs to isolate changes and dispatching a dedicated code-reviewer subagent, it ensures that every feature or bug fix is validated against original requirements. This skill is essential for subagent-driven development, providing clear protocols for handling feedback across different severity levels—from critical blockers to minor stylistic suggestions—thereby preventing technical debt from cascading through a project.

Key Features

Template-based subagent dispatching for consistent reviews
Git-integrated change detection using SHA comparison
Categorized feedback loops for Critical, Important, and Minor issues
Seamless integration with multi-task development plans
Pre-merge verification workflows for main branch protection
4 GitHub stars

Use Cases

Performing final quality checks before merging pull requests to main
Validating individual task completion during complex feature implementation
Getting an objective second opinion on complex refactoring or bug fixes

About

Key Features

Template-based subagent dispatching for consistent reviews
Git-integrated change detection using SHA comparison
Categorized feedback loops for Critical, Important, and Minor issues
Seamless integration with multi-task development plans
Pre-merge verification workflows for main branch protection
4 GitHub stars

Use Cases

Performing final quality checks before merging pull requests to main
Validating individual task completion during complex feature implementation
Getting an objective second opinion on complex refactoring or bug fixes