review-diff

Scan git diffs for predefined coding anti-patterns and mistakes.

64|19|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/faizkhairi/claude-code-blueprint --skill review-diff-faizkhairi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-diff
Source: https://github.com/faizkhairi/claude-code-blueprint/tree/main/skills/review-diff
Command: npx skills add https://github.com/faizkhairi/claude-code-blueprint --skill review-diff-faizkhairi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of scanning git diffs for project-specific anti-patterns, helping developers maintain code quality and consistency.

Core Features & Use Cases

  • Automated Code Review: Quickly identify and flag common coding mistakes and inconsistencies in git diffs.
  • Customizable Patterns: Define and scan for specific anti-patterns relevant to your project.
  • Use Case: Use this Skill to ensure that new code adheres to your project's coding standards, such as avoiding filter logic mismatches, soft-delete violations, and API call pattern inconsistencies.

Quick Start

Scan the diff for anti-patterns in the current branch using: /review-diff scan diff

Frequently Asked Questions about review-diff

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

FAQPage Schema
How do I scan a git diff for code quality issues and anti-patterns?

To scan a git diff for code quality issues and anti-patterns, execute the scan diff command within your development environment. This automatically scans added lines in your current branch for predefined coding mistakes and provides actionable recommendations.

Can I customize the patterns used to review my git diff?

Yes, you can define and customize specific anti-patterns relevant to your project. This allows the automated code review to target project-specific coding standards, such as avoiding filter logic mismatches, soft-delete violations, and API call inconsistencies.

Do I need a specific environment to automatically review git diffs for coding mistakes?

Automated git diff review requires access to a local git repository and the ability to execute git commands within your development environment. It operates by directly scanning the added lines in your current git diff output.

What is the best way to catch soft-delete violations before committing code?

The best way to catch soft-delete violations before committing is to scan your git diff for predefined anti-patterns. This automated code review process flags inconsistencies in added lines, ensuring new code adheres to your project's specific coding standards.

Why should I use an automated tool instead of manually reviewing my git diff?

Automating the identification of common coding mistakes in git diffs ensures consistent code quality without manual effort. It quickly flags project-specific anti-patterns and inconsistencies in added lines, providing targeted recommendations that maintain your coding standards.