When is code review mandatory using this skill?

Review is mandatory after each task in subagent-driven development, after completing major features, and before merging into the main branch.

What should I do if the reviewer subagent provides incorrect feedback?

You should push back with technical reasoning, provide code or tests that prove your implementation works, and request further clarification.

How does the subagent identify what to review?

The skill utilizes git SHAs (BASE_SHA and HEAD_SHA) to pinpoint the exact range of commits and changes that require evaluation.

How are issues prioritized by the code-reviewer subagent?

Issues are categorized as Critical (fix immediately), Important (fix before proceeding), or Minor (note for later) to help manage technical debt.

Requesting Code Review

Name: Requesting Code Review
Author: abudhahir

byabudhahir

•

Collaboration Tools

Automates the process of dispatching a specialized subagent to perform comprehensive code reviews during development.

About

This skill enables Claude to proactively manage code quality by dispatching a dedicated code-reviewer subagent. It helps identify logic errors, architectural issues, and missing requirements before they propagate through the codebase. By leveraging git SHAs and structured feedback loops, it ensures that every feature or task meets quality standards before merging, facilitating a robust subagent-driven development workflow that catches issues early and often.

Key Features

Automated subagent dispatching for specialized code analysis
1 GitHub stars
Git SHA-based diff analysis between base and head commits
Template-based review requests for consistent and thorough evaluation
Integration with subagent-driven development and execution plans
Structured feedback categorization into Critical, Important, and Minor issues

Use Cases

Pre-merge quality assurance to catch bugs before main branch integration
Verifying task completion in multi-step development plans
Gaining a fresh perspective when stuck on complex refactoring or bug fixes

About

Key Features

Automated subagent dispatching for specialized code analysis
1 GitHub stars
Git SHA-based diff analysis between base and head commits
Template-based review requests for consistent and thorough evaluation
Integration with subagent-driven development and execution plans
Structured feedback categorization into Critical, Important, and Minor issues

Use Cases

Pre-merge quality assurance to catch bugs before main branch integration
Verifying task completion in multi-step development plans
Gaining a fresh perspective when stuck on complex refactoring or bug fixes