review-code

Analyze git diffs to identify, reproduce, and resolve code defects.

7|Updated May 28, 2026
One-click install
npx skills add https://github.com/zcaceres/skills --skill review-code-zcaceres
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-code
Source: https://github.com/zcaceres/skills/tree/main/skills/review-code
Command: npx skills add https://github.com/zcaceres/skills --skill review-code-zcaceres

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the fragmented and error-prone nature of manual code reviews by providing a structured, repeatable pipeline that moves from initial diff analysis to automated reproduction and verified implementation.

Core Features & Use Cases

  • Structured Review: Automatically diffs branches and generates a numbered list of actionable findings.
  • Automated Reproduction: Validates findings by executing code, filtering out false positives before any fixes are planned.
  • Safe Fix Application: Plans and applies fixes only after explicit user approval, ensuring no regressions are introduced.
  • PR Comment Integration: Fetches and manages inbound feedback from human reviewers on GitHub pull requests.

Quick Start

Ask the agent to review the current branch changes and suggest fixes for any identified bugs.

Frequently Asked Questions about review-code

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate code review and bug reproduction from a git diff?

Automated code review uses a multi-step pipeline to analyze git diffs, execute code to reproduce defects, and plan verified fixes. It generates a numbered list of actionable findings while filtering out false positives before applying changes.

How do I manage and resolve inbound feedback on GitHub pull requests?

Managing inbound pull request feedback involves fetching review comments via the GitHub CLI and integrating them into the local branch workflow. The pipeline analyzes these comments alongside git diffs to reproduce reported issues and apply approved resolutions.

Do I need the GitHub CLI to interact with pull request comments during a code review?

Yes, the GitHub CLI is required for pull request interaction. Standard git tooling handles local diff generation and branch management, but the CLI is necessary to fetch and manage inbound feedback from human reviewers on GitHub.

What is the safest way to apply automated fixes during code refactoring?

Safe automated fix application requires explicit user approval before any changes are made. The pipeline plans and applies fixes only after validation to ensure no regressions are introduced into the local repository branch.

How does automated bug reproduction prevent false positives in code reviews?

Automated bug reproduction validates findings by executing code to confirm the defect exists. This filtering process removes false positives from the initial diff analysis before any fix planning or implementation begins.

Can I use an automated code review pipeline on local repository branches?

Yes, the pipeline operates directly on local repository branches using standard git tooling. It generates diffs for branch comparison and manages local changes while optionally integrating with GitHub pull requests.