review-changes
Review the current branch diff for correctness, reuse and governance, then adversarially verify each finding and report only the ones that survive refutation. Use when asked to "review my changes", "review this branch", "review the diff", "review trước khi push", or before opening a PR — for an unlanded design document use spec-red-team instead.
- License 许可
- MIT
- 所属仓库
- baodq97/govkit
- 最近更新
- 2026-09-07
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- review-changes
- context
- fork
- description
- Review the current branch diff for correctness, reuse and governance, then adversarially verify each finding and report only the ones that survive refutation. Use when asked to "review my changes", "review this branch", "review the diff", "review trước khi push", or before opening a PR — for an unlanded design document use spec-red-team instead.
03 SKILL.md 正文
/review-changes
A thin front onto the .claude/workflows/review-changes.js orchestration — the review->verify
pipeline that reviews the current branch diff across independent dimensions
(correctness, reuse, governance), then adversarially verifies each finding, surfacing only
the issues that survive refutation. Invoke review-changes.js (pass your own dimensions via
args or take the default three); the pipeline has no barrier — a dimension's findings verify as
soon as that dimension's review completes. This wrapper reimplements none of that logic — the
.js stays the single source of truth.
By-hand fallback — workflows are research-preview and globally disableable
Workflows are research-preview and globally disableable (disableWorkflows /
CLAUDE_CODE_DISABLE_WORKFLOWS=1) and cannot be bundled in a plugin (there is no workflows
field in plugin.json). If review-changes.js does not run, drive the SAME order BY HAND: for
each dimension dispatch swe-flow:reviewer over the diff (inspect both the committed branch diff
and any uncommitted/untracked changes — untracked files are NOT in git diff); for each finding,
dispatch a second swe-flow:reviewer to refute it, defaulting to refuted when it cannot be
reproduced; keep only the findings that survive. Nothing is lost — the govkit PreToolUse/Stop
hook + CI govkit verify gate every governed doc regardless. The workflow is an accelerant, not
the source of truth.
This wrapper dispatches only the subagent review-changes.js already dispatches —
swe-flow:reviewer (one per dimension for review, a second per finding for refutation). It
introduces no new agent type or skill. It only triages code review: it never flips a governed-doc
status: and never assigns an owner (AGENTS.md § Agent constraints).
04 同仓库更多 Skills
trigger-shaped
Use when the user says "plan a sprint retro"; drafts retro/notes.md for the team.
terse-unguarded
Step 2 — writes docs/x/output.json quietly.
guarded
Summarizes ledger totals into reports/monthly.csv.
open
Draft a spec. Use when asked to "draft a spec" or "write the RFC".
guarded
Deploy the thing.
working-discipline
Thinking-checkpoint discipline for substantive implementation, debugging, or autonomous work — 21 trigger-gated items (trigger → mandatory question → evidence to produce) that cut agent error and human escalation. Use before an autonomous or long-running run, when asked to "work carefully", "double-check", "làm cẩn thận", "reduce errors", "be more autonomous", or after looping twice on the same failing fix. NOT a procedure — checkpoints fire on their triggers and demand evidence, with an N/A escape valve so a strong model pays near-zero overhead.