How should I handle feedback from the AI reviewer?

Critical issues should be fixed immediately, and important issues should be addressed before moving on. For minor issues or incorrect feedback, you can push back with technical reasoning.

How does the code review subagent analyze my work?

The subagent uses git SHAs to identify specific changes made between two points in time and compares that code against your provided requirements or plan to ensure alignment.

Is it mandatory to use this skill for every change?

While optional for minor tweaks, it is highly recommended after every task in subagent-driven development and mandatory before merging major features to the main branch.

Can this skill help when I'm stuck on a bug?

Yes, requesting a code review when stuck provides a fresh perspective and can help identify logic errors or edge cases you might have overlooked.

Automated Code Review

Name: Automated Code Review
Author: dkyazzentwatwa

bydkyazzentwatwa

•

Herramientas de Colaboración

Facilitates high-quality code reviews by dispatching a specialized reviewer subagent to identify bugs and verify implementation requirements.

Acerca de

The Automated Code Review skill streamlines the quality assurance process within Claude Code by automating the dispatch of a code-reviewer subagent. By analyzing the delta between specific git SHAs, this skill evaluates recent implementations against project requirements to catch critical issues early in the development lifecycle. It provides a structured feedback loop—categorizing findings into critical, important, and minor issues—ensuring that developers maintain high standards during subagent-driven development and before final merges.

Características Principales

Severity-based feedback categorization (Critical, Important, Minor)
29 GitHub stars
Git SHA-based change tracking and delta review
Seamless integration with subagent-driven development workflows
Automated subagent-driven code analysis
Requirement verification against project plans and documentation

Casos de Uso

Obtaining an objective second perspective on complex refactors or bug fixes
Pre-merge quality assurance to prevent regressions and bugs
Verifying task completion in multi-step development plans

Acerca de

Características Principales

Severity-based feedback categorization (Critical, Important, Minor)
29 GitHub stars
Git SHA-based change tracking and delta review
Seamless integration with subagent-driven development workflows
Automated subagent-driven code analysis
Requirement verification against project plans and documentation

Casos de Uso

Obtaining an objective second perspective on complex refactors or bug fixes
Pre-merge quality assurance to prevent regressions and bugs
Verifying task completion in multi-step development plans