code-review

Review Git code changes for correctness, security, performance, and maintainability.

16|3|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/zbruhnke/claude-code-starter --skill code-review-zbruhnke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/zbruhnke/claude-code-starter/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/zbruhnke/claude-code-starter --skill code-review-zbruhnke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of reviewing code for quality, security vulnerabilities, and adherence to best practices, ensuring higher code integrity before merging.

Core Features & Use Cases

  • Automated Code Analysis: Reviews staged or unstaged code changes against project standards and general best practices.
  • Security & Performance Checks: Identifies potential security risks, performance bottlenecks, and logic errors.
  • Use Case: Before merging a pull request, use this Skill to get a comprehensive review of the changes, catching bugs and security flaws early in the development cycle.

Quick Start

Ask the code-review skill to review the staged changes in the current repository.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review staged Git changes for security vulnerabilities and best practices?

To review staged Git changes for security vulnerabilities and best practices, this Skill analyzes your code diff against project standards and general quality rules. It identifies potential security risks and logic errors before merging.

Can I check unstaged code modifications in my repository for performance bottlenecks?

Yes, you can check unstaged code modifications for performance bottlenecks. The Skill applies comprehensive analysis to both staged and unstaged changes, identifying performance issues, security flaws, and maintainability concerns.

How does automated code review work with project-specific standards?

Automated code review works with project-specific standards by referencing the CLAUDE.md file in your repository. The Skill uses Git diff, Grep, Glob, and Bash tools to check your changes against these defined rules.

What is the best way to catch bugs early in the development cycle before a pull request?

The best way to catch bugs early before a pull request is to run an automated code analysis on your modifications. This Skill reviews your code changes for correctness and security, ensuring higher code integrity before merging.

Does this code review tool work without any external dependencies?

Yes, this code review tool works without external dependencies. It operates entirely within your Git repository using built-in tools like Bash, Grep, and Glob to analyze staged or unstaged code modifications.

When should I avoid using automated code analysis for my Git repository?

You should avoid using automated code analysis when you need to review code outside a Git repository or when project-specific standards are not defined in a CLAUDE.md file, as the Skill relies on these for comprehensive analysis.