claude-review

Analyze local git diffs for logic flaws and rule violations.

2|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/erclx/aitk --skill claude-review-erclx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-review
Source: https://github.com/erclx/aitk/tree/main/claude/skills/claude-review
Command: npx skills add https://github.com/erclx/aitk --skill claude-review-erclx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the issue of ephemeral, inconsistent code reviews by providing a structured, persistent, and context-aware analysis of local changes before they are shipped.

Core Features & Use Cases

  • Context-Aware Analysis: Automatically incorporates project-specific rules, requirements, and architecture documents to ensure findings align with project standards.
  • Structured Reporting: Generates a persistent, severity-graded report on disk that serves as a reliable receipt for the ship process.
  • Use Case: Use this skill when you have finished a feature branch and need to ensure your changes comply with project rules and logic requirements before merging, avoiding the need for manual, repetitive checklist reviews.

Quick Start

Run the claude-review skill to analyze the current branch changes against the project context and generate a findings report.

Frequently Asked Questions about claude-review

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

FAQPage Schema
How do I automate local code review for branch integrity before merging?

You can automate local code review by running the skill against your current branch changes. It analyzes local git diffs against project-specific documentation and coding standards to generate a structured, severity-graded findings report.

What is context-aware static analysis for local git diffs?

Context-aware static analysis for local git diffs evaluates uncommitted or staged changes by incorporating project-specific rules and architecture documents. This ensures findings align with project standards rather than subjective feedback.

How do I generate a severity-graded code review report for uncommitted changes?

To generate a severity-graded code review report for uncommitted changes, run the skill on your local branch. It produces a persistent report on disk that serves as a reliable receipt for your ship process.

Do I need git access and project context files for automated code review?

Yes, automated code review requires git access and adherence to defined project context files. These inputs ensure the analysis provides high-signal, non-subjective feedback based on your specific coding standards.

Can I review staged changes without committing them to the branch?

You can review staged changes without committing them by running the skill on staged or uncommitted modifications. It operates on these local git diffs to identify logic flaws and rule violations before they are shipped.

When should I use automated static analysis instead of manual checklist reviews?

Automated static analysis should be used when you finish a feature branch and need to ensure changes comply with project rules. It avoids the need for manual, repetitive checklist reviews by providing a structured, persistent report.