review

Review staged git diffs against CLAUDE.md rules before commit.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps ensure code changes conform to project rules by reviewing diffs before they are committed, catching issues early.

Core Features & Use Cases

  • Diff analysis: Compares staged and unstaged changes to identify scope violations, size issues, and edge cases.
  • Rule-aware checks: Verifies changes against referenced CLAUDE.md rules and architectural constraints.
  • Pre-commit guidance: Suggests actionable next steps to improve code quality before commit.

Quick Start

Run a pre-commit review of your current changes to verify quality before committing.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review staged git changes before committing?

To review staged git changes before committing, run a pre-commit review against your project rules to analyze diffs and catch violations early. It compares staged and unstaged modifications to identify scope and sizing issues, providing actionable guidance.

Can I check my code diff against CLAUDE.md architectural rules?

Yes, you can check your code diff against CLAUDE.md rules. The review process verifies staged changes against referenced architectural constraints to ensure modifications conform to defined project rules before being committed.

What is a pre-commit code review for scope and edge cases?

A pre-commit code review for scope and edge cases is a workflow step that analyzes git diffs to verify sizing, identify boundary conditions, and ensure test coverage before changes are finalized. It helps catch issues early.

Does the pre-commit review process require a specific git environment setup?

The pre-commit review process requires access to git, CLAUDE.md rules, and a defined set of checks to perform during the review. Your code base must be configured to allow diff analysis during development workflows.

What is the best way to catch quality violations before a git commit?

The best way to catch quality violations before a git commit is to run an automated review of your staged changes. This analyzes the diff against project rules, detecting scope violations and edge cases to provide actionable next steps.

Why should I use a pre-commit review instead of checking code after committing?

You should use a pre-commit review to catch issues early, ensuring code changes conform to project rules before they enter the commit history. Reviewing staged diffs prevents scope violations and sizing issues from being committed.