How does the skill identify which code to review?

The skill uses git SHAs (BASE_SHA and HEAD_SHA) to define the exact range of commits that need to be analyzed by the code-reviewer subagent.

Can this skill be integrated into my existing workflow?

Yes, it is designed to work with subagent-driven development, plan execution, and ad-hoc coding by providing clear checkpoints for quality assurance.

What should I do if the AI reviewer identifies an issue?

You should fix Critical issues immediately and Important issues before proceeding. Minor issues can be noted for later. If the reviewer is incorrect, you should push back with technical reasoning.

When should I use the Requesting Code Review skill?

It is mandatory after each task in subagent-driven development, after completing major features, and before merging to the main branch. It is also useful when you are stuck or before starting a refactor.

Requesting Code Review

Name: Requesting Code Review
Author: januarfonti

byjanuarfonti

Collaboration Tools

Automates and standardizes the process of requesting high-quality AI code reviews using specialized subagents and git integration.

About

This skill facilitates a structured code review process within the Claude Code environment by dispatching a dedicated code-reviewer subagent. It helps developers maintain high code quality by enforcing review milestones after task completion, major feature implementation, or before merging branches. By utilizing git SHAs to define scope and a standardized template for context, the skill ensures that feedback is targeted, actionable, and categorized by severity, ultimately preventing technical debt from accumulating during subagent-driven development.

Key Features

Severity-based issue categorization (Critical, Important, Minor)
Automated subagent dispatch for specialized code analysis
Standardized review templates for consistent feedback quality
Seamless integration with subagent-driven development workflows
0 GitHub stars
Git-integrated review scope definition using commit SHAs

Use Cases

Verifying a major feature meets requirements before merging into the main branch
Conducting incremental reviews after every task in a multi-step development plan
Getting a fresh perspective and baseline check before performing complex refactoring

About

Key Features

Severity-based issue categorization (Critical, Important, Minor)
Automated subagent dispatch for specialized code analysis
Standardized review templates for consistent feedback quality
Seamless integration with subagent-driven development workflows
0 GitHub stars
Git-integrated review scope definition using commit SHAs

Use Cases

Verifying a major feature meets requirements before merging into the main branch
Conducting incremental reviews after every task in a multi-step development plan
Getting a fresh perspective and baseline check before performing complex refactoring