Diff review
Workflow awareness for claude-diff-review. Informs Claude that file edits are being tracked and reviewed interactively. Use when editing files in a session where claude-diff-review is active.From its SKILL.md
npx -y skills add Gorluxor/Claude-Code-Diff-Review --skill diff-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.7 KB, as published. Nobody here has run it
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, andMultiEditoperations are auto-approved - Originals are preserved — the first version of each file is kept as a shadow copy
- Interactive review happens after your response — the user reviews diffs with per-hunk accept/reject when you finish
- Multi-round editing — if the user rejects changes, you will be re-engaged with details of what was rejected/modified
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
- When re-engaged after rejection: read the rejection details, acknowledge the user's edits, and ask if they want further changes
What happens after your response
- The Stop hook fires and opens interactive review (VS Code diff editor or terminal per-hunk review)
- The user accepts, rejects, or modifies changes per file/hunk
- If rejections or modifications occurred, you are re-engaged with a summary
- If all changes are accepted, the session ends normally
- The user runs
claude-diff acceptto finalize and clean up shadow copies