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.
소스 정보
- 저장소
- skeletorflet/opencode-supreme-setup
- 최근 소스 활동
- 2026년 5월 19일 18:56
- 감지된 SKILL.md 언어
- 영어
- 스타
- 48
- 포크
- 2
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
파일 탐색기
3 개 파일SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- 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.
GitHub에서 보기