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.
Datos de origen
- Repositorio
- skeletorflet/opencode-supreme-setup
- Última actividad en el origen
- 19 de mayo de 2026 a las 18:56
- Idioma detectado de SKILL.md
- inglés
- Estrellas
- 48
- Forks
- 2
Opciones de instalación
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Revisa los archivos de origen
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Explorador de archivos
3 archivosMostrando SKILL.md
SKILL.md
Instrucciones de origen · Vista previa de solo lectura- name
- diff-review
- description
- 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.
- od
- {"scenario":"code-migration","mode":"review"}
# 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 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
Reserved id, prompt-only fragment in v1.
Ver en GitHub