code-review

Review git diffs for reuse, quality, and efficiency issues.

3|1|Updated Apr 1, 2026

Search Tags:#automation #efficiency #quality #code-review #reuse #git-diff

Ready to run

npx skills add https://github.com/bhaumikmaan/claude-code-master-skills --skill code-review-bhaumikmaan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/bhaumikmaan/claude-code-master-skills/tree/main/skills/code-review
Command: npx skills add https://github.com/bhaumikmaan/claude-code-master-skills --skill code-review-bhaumikmaan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often struggle to efficiently review code changes for reuse, quality, and performance while staying token‑efficient and avoiding full‑codebase scans. This Skill focuses the review on the exact diff, orchestrates thorough analysis, and consolidates actionable fixes.

Core Features & Use Cases

Three‑Pass Review: Separate parallel passes for code reuse, quality, and efficiency.
Diff‑First Approach: Starts from git diff or recent modified files, never the whole repository.
Parallel Agents: Launches sub‑agents for large diffs to speed up analysis.
Consolidation & Fixing: Aggregates findings, applies fixes, and runs build/test/lint.
Project Customization: Reads user-config.md to tailor smells, style guides, and verification commands.
Use Cases: Pre‑merge PR review, post‑implementation audit, quick simplification before deployment, or any scenario needing structured code improvement.

Quick Start

Run the code-review skill on the current git diff to get a consolidated list of reuse, quality, and efficiency improvements.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I review a git diff for code quality and reuse opportunities?▼

To review a git diff for code quality and reuse, apply a three-pass review approach that analyzes the exact diff for reuse opportunities, quality issues, and efficiency problems in parallel, then consolidates actionable fixes.

Can I automate pre-merge code review to check only modified files?▼

Yes, you can automate pre-merge code review by running a diff-first analysis on modified files, launching parallel sub-agents to speed up large diffs, and then applying consolidated fixes and running build/test/lint commands.

What is a three-pass code review and when should I use it?▼

A three-pass code review separates analysis into parallel passes for code reuse, quality, and efficiency. Use it during pre-merge PR checks, post-implementation audits, or refactoring sessions to get structured, token-efficient code improvements.

Does this code review approach require scanning the whole repository?▼

No, this code review approach does not require scanning the whole repository. It uses a diff-first approach that starts directly from the git diff or recently modified files to stay token-efficient and focused on actual changes.

How do I customize code review rules for my project's style guide?▼

You can customize code review rules by providing a user-config.md file to tailor detected code smells, style guides, and verification commands, ensuring the review adheres to your specific project requirements and token-efficiency hierarchies.

What is the best way to handle large diffs during an automated code review?▼

The best way to handle large diffs during an automated code review is to orchestrate parallel review agents that analyze the changes concurrently, consolidating findings and applying fixes while running build, test, and lint commands.