Skip to content

Diff Review

Shows code changes as a reviewable diff and records your accept or reject decision

Stars
105,448
Licence
Apache-2.0
Files
2 files

What it does

When an agent has edited code as part of a larger migration or patch run, this skill gathers those changes into a standard diff file and a plain-language per-file summary. It then presents a choice (accept all, reject all, or accept partially) so you decide what stays. Your decision is saved in a small decision file, and rejected changes are rolled back using git.

Great for

  • Developers reviewing agent-made code migrations before they are kept
  • Teams that want a human sign-off step on automated patches
  • People running the open-design project's code-migration workflow

Skip it if

  • Solo quick edits where a normal git diff and commit review is enough, since this adds a multi-file workflow
  • Repositories where you do not want the agent running git restore, because rejection rolls back files and can discard work if the patch boundary is wrong

Try asking

  • “Review the changes from the last migration run and let me accept or reject them per file”
  • “Show me a diff summary of what the patch run changed before anything is committed”
  • “Partially accept the patch: keep the changes to the config files but reject the rest”
Step-by-step guide: how to use Diff ReviewInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 2 original files, the Apache-2.0 licence and an attribution note.

    diff-review.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip diff-review.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip diff-review.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Make sure your repository is committed or backed up before accepting or rejecting a patch, since rollback affects working files.
  • Use partial decisions for large patches so you can review each file separately.
  • Check the generated review/summary.md before choosing accept to confirm the scope matches plan/steps.json.

What's inside

  • open-design.json
  • SKILL.md

Redistributed unmodified from nexu-io/open-design under the Apache-2.0 licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.