用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/dikamilo/dx-workflow --skill dx-review-triage命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
Archive a completed change or effort — move its folder to context/archive/ and stamp it archived.
Record one finding — a warning or a decision-with-rationale — as an append-only entry in foundation/lessons.md.
Start a new piece of work — creates a change or an effort and points you at the next step.
基于 SOC 职业分类
正在显示 SKILL.md
| name | dx-review-triage |
| description | Triage findings from a plan-review or impl-review report and apply the fixes you choose. |
| disable-model-invocation | true |
| argument-hint | [change-id] [plan|impl] |
Turn a review report's findings into decisions — and, when you say so, into edits. dx-plan-review and dx-impl-review only analyze and report; this is the one place that acts on a finding, editing plan.md or the code it reviewed, one finding at a time, only on your confirmation. That split keeps both review gates pure: a reviewer that never fixes what it checks doesn't need to graduate into a tool-restricted agent.
Guard. Resolve <change-id> under context/changes/. reviews/ must contain plan-review.md or impl-review.md — if the directory is missing or empty, point at /dx-plan-review or /dx-impl-review instead. If the path is under context/archive/, refuse: archived work is done.
The review-report reference (invoke dx-references with review-report) — the finding-ID/Resolution schema, the resume rule, and the file conventions this skill reads and writes.
Each type has exactly one file — reviews/plan-review.md or reviews/impl-review.md — always the current review, since re-running dx-plan-review/dx-impl-review overwrites rather than dating a new file. A second argument names the type (plan or impl) directly. No argument: exactly one file present → use it; both present → ask which, since a plan-review and an impl-review can each carry open findings on the same change at once.
plan.md in full — this is what gets edited.dx-impl-review used to review: git log/git diff for the commits that landed this change's phases, plus the specific files each pending finding names. Don't reload files findings you're skipping don't touch.Resume per the review-report reference: the first finding with Resolution: PENDING, document order. For each, show its title, location, detail, and suggested fix, then ask:
/dx-lesson's entry shape and tell the user to confirm there. Never append to foundation/lessons.md yourself — that file has exactly one writer.Immediately rewrite that finding's Resolution: line in place per the reference's rules. If an edit you already applied for an earlier finding also resolves a later one (one fix closing both a Plan-Drift and the Safety finding it caused, say), mark the later finding FIXED too, pointing at the same edit — don't manufacture a redundant second edit or commit just to keep one fix per finding.
dx-implement uses: fix(<change-id>): <finding title> (review).plan.md only. dx-plan never commits the plan itself, so neither does this.plan-review.md/impl-review.md), in either case — it's working state like plan.md, not a deliverable; the user commits it on their own schedule.If applying a fix would contradict something the plan or a standard states elsewhere, stop and say so — don't silently pick a side.
Every finding in the resolved report has a Resolution: other than PENDING — or you've stopped partway, which is fine, since re-running resumes from the next pending one. Print a one-line tally and stop, no auto-chain:
Triaged <report file>: <n> fixed, <n> skipped, <n> accepted, <n> dismissed
Next: /dx-plan-review <change-id> or /dx-implement <change-id> (plan-review triaged)
or: /dx-impl-review <change-id> or /dx-archive <change-id> (impl-review triaged)