diff-review

Analyze uncommitted and staged Git code changes for correctness, security, bugs, style, and completeness.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/bswrundquist/devtools --skill diff-review-bswrundquist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diff-review
Source: https://github.com/bswrundquist/devtools/tree/main/src/devtools/templates/claude/user/.claude/skills/diff-review
Command: npx skills add https://github.com/bswrundquist/devtools --skill diff-review-bswrundquist

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers catch issues in their code changes early by providing a systematic review process for uncommitted or staged changes, preventing bugs and security vulnerabilities from entering the codebase.

Core Features & Use Cases

  • Comprehensive Change Analysis: Reviews code for correctness, security, potential bugs, style consistency, and completeness.
  • Pre-Commit Quality Gate: Acts as a lightweight pre-commit hook to ensure code quality before it's committed.
  • Use Case: Before committing a new feature, run this Skill to get a detailed report on potential issues, ensuring a cleaner commit history and reducing the likelihood of merge conflicts or bugs in production.

Quick Start

Use the diff-review skill to analyze your uncommitted and staged code changes for potential issues.

Frequently Asked Questions about diff-review

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

FAQPage Schema
What is a pre-commit code review and why should I run one?

A pre-commit code review systematically analyzes uncommitted and staged code changes for correctness, security, potential bugs, style, and completeness to catch issues early before they enter the codebase.

How do I review staged code changes for potential bugs and security issues?

To review staged code changes, use a tool that leverages Git diffing to analyze your modifications across multiple dimensions, providing a detailed report on potential bugs, security vulnerabilities, and style consistency.

Does this code review method require Git to analyze uncommitted changes?

Yes, this code review method requires Git for diffing. It uses Git to identify uncommitted and staged changes, then systematically analyzes those diffs for correctness, security, and completeness.

What is the best way to check code quality before committing new features?

The best way to check code quality before committing is to run a systematic analysis on your staged changes, acting as a lightweight pre-commit quality gate to ensure a cleaner commit history and reduce production bugs.

Can I use this pre-commit review to check both correctness and style consistency?

Yes, you can use this pre-commit review to check both correctness and style consistency. It analyzes uncommitted code changes across multiple dimensions, including potential bugs, security, style, and completeness.