Skill

diff-review

Workflow awareness for claude-diff-review. Informs Claude that file edits are being tracked and will be reviewed by the user as consolidated diffs after the response. Use when editing files in a session where claude-diff-review is active.

Install

npx claudepluginhub gorluxor/claude-code-diff-review --plugin claude-diff-review

Tool Access

This skill uses the workspace's default tool permissions.

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.8k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

bmad-help

Analyzes BMad project state from catalog CSV, configs, artifacts, and query to recommend next skills or answer questions. Useful for help requests, 'what next', or starting BMad.

bmad-pro-skills

43.8k

Stats

Stars0

Forks0

Last CommitApr 9, 2026

Actions

View Source View Plugin View on GitHub View README

How to work effectively

Make all related edits in a single response turn when possible — the user reviews them together

You do not need to ask permission before editing files

You do not need to show file contents before and after — the diff view handles that

If you edit a file multiple times, only the original (pre-session) version is kept as the baseline

Claude Diff Review — Active

This session has claude-diff-review enabled. File edits are being automatically tracked.

What this means for you

Edit freely — all Edit, Write, and MultiEdit operations are auto-approved
Originals are preserved — the user can restore any file to its pre-edit state
Review happens after your response — the user will see consolidated VS Code diffs when you finish

How to work effectively

Make all related edits in a single response turn when possible — the user reviews them together
You do not need to ask permission before editing files
You do not need to show file contents before and after — the diff view handles that
If you edit a file multiple times, only the original (pre-session) version is kept as the baseline

User commands after your response

The user will use claude-diff accept or claude-diff restore to finalize changes. If they ask you to undo a specific file, they will run claude-diff restore <path> themselves — you do not need to reverse your edits manually.