claude-review-code

Delegates git diff review to the Claude Code CLI running Opus at xhigh reasoning effort.

2|Updated May 16, 2026
One-click install
npx skills add https://github.com/avbel/ai-skills --skill claude-review-code-avbel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: claude-review-code
Source: https://github.com/avbel/ai-skills/tree/main/skills/claude-review-code
Command: npx skills add https://github.com/avbel/ai-skills --skill claude-review-code-avbel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Getting an independent, high-effort second opinion on local code changes is hard to standardize: reviewers vary in rigor, and quick self-reviews miss subtle bugs. This Skill runs a consistent, maximal-effort external review of your working tree or branch diff without ever modifying your code. ## Core Features & Use Cases - Automated scope detection: Reviews staged, unstaged, and untracked working-tree changes, or falls back to a branch diff against an auto-resolved base (origin/HEAD, main, or master). - Forced heavyweight configuration: Pins the review to Opus at xhigh reasoning effort regardless of the calling session's model, with an optional adversarial stance that tries to break confidence in the change. - Hardened read-only execution: Pipes the review brief over stdin, restricts the agent to Read/Grep/Glob tools, denies edits, shell, and network access, and fences untrusted diff content against prompt injection. - Use Case: Before merging a new feature branch, run the script with --scope branch --base develop --adversarial to get a severity-ranked findings report with a ship/no-ship verdict. ## Quick Start Ask the agent to review my current uncommitted changes with Claude for a second opinion before I merge.

Frequently Asked Questions about claude-review-code

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

FAQPage Schema
How do I get a second-opinion code review of my git changes?▼

Run the review.sh script inside your git repository; it detects staged, unstaged, and untracked changes, builds a review brief, and pipes it to the Claude Code CLI. The review streams to stdout as a Markdown report with a verdict and severity-ranked findings.

How do I review a branch diff against a specific base branch?▼

Pass --scope branch --base <ref> to review the diff between that base and HEAD, for example --base develop. If no base is given, it auto-resolves to origin/HEAD, then main, then master.

Does this code review skill modify or fix my code?▼

No, it is strictly review-only and never edits, fixes, or stages anything. The agent is restricted to Read, Grep, and Glob tools, with Edit, Write, Bash, and network tools explicitly denied at the tool layer.

What are the requirements for running a Claude CLI code review?▼

You need the claude CLI installed on PATH and authenticated (sign in once interactively or set ANTHROPIC_API_KEY), and you must run inside a git working tree. A coreutils timeout or gtimeout binary is optional for enforcing the wall-clock cap.

Why does the code review time out on large diffs?▼

Opus at xhigh reasoning effort is deliberately slow, and the default timeout is 15 minutes. Raise it with --timeout (for example --timeout 30m) or narrow the review scope to fewer files.

Is it safe to review untrusted third-party code with this approach?▼

The skill fences untrusted diff content and restricts the agent to read-only tools, but the agent can still read repository files. For untrusted code such as a stranger's PR, run the review inside a container or VM with no access to credentials or secrets.