diff-review
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.
Profile →npx skills add nexu-io/open-design --skill diff-review --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 ```text 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 re
- Inputs
- Output
- Convergence
- Anti-patterns the prompt fragment forbids
- Status
What does the diff-review skill do?
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.
How do I install it?
Run `npx skills add nexu-io/open-design --skill diff-review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From nexu-io/open-design, a repository with 83,577 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.