nexu-io/open-design
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.
npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/atoms/diff-review"Source checked Jul 28, 2026·Refresh due Oct 26, 2026
Reorganized from the pinned upstream SKILL.md
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.
npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/atoms/diff-review"The pinned source supports a structured brief, but not an expanded tutorial. Only detected inputs, outputs, and sections are shown.
219 source words · 5 usable sections
Review inputs
Evidence and findings
Review workflow
Sections are extracted automatically from the pinned SKILL.md and link back to the source.
The project cwd's accumulated edits since the run started (or
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.
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-…
Skipping the surface and assuming acceptance.
Review checklist
The source section “Inputs” has been checked.
The source section “Output” has been checked.
The source section “Convergence” has been checked.
The source section “Anti-patterns the prompt fragment forbids” has been checked.
Source output checked: 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.
FAQ
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.
The source record exposes this install command: npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/atoms/diff-review". Inspect the command and pinned source before running it.
Quality breakdown
Based on traceable docs and repository signals; stars are not treated as quality.
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.
plan/steps.json for context per file.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.
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.
decision.json that lacks accepted_files /
rejected_files on partial decisions.plan/steps.json's union of
files[] — the patch boundary is a contract.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.