How does the skill identify which code to review?

The skill uses Git SHAs (Base and Head) to identify the specific range of commits that require analysis, ensuring the subagent focuses only on relevant changes.

What does the Requesting Code Review skill actually do?

It triggers a specialized 'code-reviewer' subagent to examine your recent code changes and compare them against your project requirements or implementation plans to ensure accuracy.

When should I use this Claude Code skill?

It is recommended after completing major tasks, before merging code into your main branch, or whenever you need a technical second opinion on a complex implementation.

What kind of feedback does the subagent provide?

The reviewer categorizes findings into Critical, Important, and Minor issues, while also highlighting the strengths of your implementation to provide a balanced assessment.

Automated Code Review

Name: Automated Code Review
Author: NickCrew

byNickCrew

•

Herramientas de Colaboración

Dispatches a specialized subagent to perform comprehensive code reviews against implementation plans and technical requirements.

Acerca de

The Requesting Code Review skill facilitates robust quality control within the Claude Code environment by automating the peer review process. It allows developers to dispatch a specialized 'code-reviewer' subagent to analyze specific changes—defined by Git SHAs—against an original implementation plan or set of requirements. By identifying critical issues, logic errors, and architectural inconsistencies early, this skill ensures high-quality code output and prevents technical debt from cascading through complex development cycles.

Características Principales

Seamless integration with subagent-driven development workflows
Prioritized feedback categorizing issues as Critical, Important, or Minor
Automated subagent dispatch for deep code analysis
Git-integrated review using specific commit SHAs
7 GitHub stars
Requirement-based verification against implementation plans

Casos de Uso

Getting an objective technical perspective when stuck or before starting a refactor
Catching logic errors and edge cases after complex bug fixes
Verifying major feature implementations against design documents before merging

Acerca de

Características Principales

Seamless integration with subagent-driven development workflows
Prioritized feedback categorizing issues as Critical, Important, or Minor
Automated subagent dispatch for deep code analysis
Git-integrated review using specific commit SHAs
7 GitHub stars
Requirement-based verification against implementation plans

Casos de Uso

Getting an objective technical perspective when stuck or before starting a refactor
Catching logic errors and edge cases after complex bug fixes
Verifying major feature implementations against design documents before merging