Agent skill · software engineering · nexu-io
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.
Why this skill is useful
Adds specific commands and workflows for rendering and managing code migration diffs that the AI wouldn't reliably generate on its own.
What it needs
About 1k tokens when loaded. Last updated 2026-08-07. 84,236 stars on the source repository.
What this skill does
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 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 acceptedfiles / rejectedfiles 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.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nexu-io/diff-review