Diff Review Agent Skill

Render the patch-edit run's accumulated changes as a reviewable diff, surface it through a GenUI choice surface, and persist the user's accept / reject decision into the artifact manifest.

740 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

83386

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/nexu-io/open-design --skill diff-review

What comes with it

896 bytes besides the instruction

open-design.json

The instruction itself

6 sections, as written by the author

Diff review

Spec §20.3 / §21.3.2: a code-migration / tune-collab handoff is

worthless without a human-reviewable diff. This atom is the

"present the patch, capture the decision" stage.

Inputs

The project cwd's accumulated edits since the run started (or

since the previous diff-review iteration).

plan/steps.json for context per file.

Output

project-cwd/
└── review/
    ├── diff.patch        # unified diff (git apply-shaped)
    ├── summary.md        # human-friendly per-file walkthrough
    ├── decision.json     # { decision: 'accept' | 'reject' | 'partial', accepted_files: [...], rejected_files: [...], reviewer: 'user' | 'agent' }
    └── meta.json         # { generatedAt, atomDigest, planRevision }

The atom raises a choice GenUI surface with the three top-level

decisions (accept / reject / partial). On partial the user

flips per-file decisions through follow-up surfaces.

Convergence

The atom completes when decision.json has a non-empty decision.

Acceptance writes handoffKind: 'patch' (or 'deployable-app'

when a successful build-test is on file) into the eventual

artifact manifest; rejection rolls back the patch via git restore

or the equivalent in the code-import-bound repo path.

Anti-patterns the prompt fragment forbids

Skipping the surface and assuming acceptance.
Generating a decision.json that lacks accepted_files /

rejected_files on partial decisions.

Rolling back files outside plan/steps.json's union of

files[] — the patch boundary is a contract.

Status

Implemented by the daemon runner in

apps/daemon/src/plugins/atoms/diff-review.ts, with GenUI decisions persisted

by apps/daemon/src/plugins/atoms/diff-review-genui-bridge.ts.

Other skills for the same job

different authors, same section of the catalogue

Receiving Code Review

by ZhanlinCui

×7

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

2k tokens

Requesting Code Review

by ZhanlinCui

×6

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

Comprehensive GitHub code review with AI-powered swarm coordination

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.

Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

2k tokens

How to use it

Copy the folder

Take nexu-io/diff-review from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.