change-traceability-review
Use for change traceability review across specs, commits, PRs, branches, local diffs, and git history, including Spec Preparation, Review Readiness Checks, and Review Retrospectives, to generate or verify Story-linked specs, commit-message evidence, test evidence, risk signals, AI involvement, and review-flow improvement suggestions.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 2.5k
- Forks
- 205
01 前言 Front Matter
- name
- change-traceability-review
- description
- Use for change traceability review across specs, commits, PRs, branches, local diffs, and git history, including Spec Preparation, Review Readiness Checks, and Review Retrospectives, to generate or verify Story-linked specs, commit-message evidence, test evidence, risk signals, AI involvement, and review-flow improvement suggestions.
02 资源文件 5
- 参考文档references/commit-contract.md1.1 KB
- 参考文档references/evidence-commands.md899 B
- 参考文档references/mode-rules.md2.1 KB
- 参考文档references/reporting.md1.4 KB
- 参考文档references/spec-contract.md1.8 KB
03 SKILL.md 正文
Change Traceability Review
Review the traceability behind a change, not code style: Story or issue -> Spec -> plan/tasks -> commit/branch/PR -> diff -> tests -> risk. Default to Chinese and keep the report compact and decision-oriented. Treat specs as the review source of truth; code is acceptable when it clearly serves the spec.
Modes
- Spec Preparation: before implementation or commit, create or tighten a Story-linked spec and define acceptance scenarios, plan/tasks, tests, and risk evidence that later commits can cite. Load Spec Contract.
- Review Readiness Check: inspect the current diff, staged diff, PR text, branch, or selected commits before review/merge. Load Mode Rules and Reporting.
- Review Retrospective: inspect recent history, usually latest 30 commits. Identify commit-message habits, weak traceability, missing Spec/Test/Risk evidence, oversized or mixed-scope commits, spec-doc patterns, and rework signals. Load Mode Rules and Reporting.
Entry and Routing
- Identify the mode from the user's request or the current review surface.
- Read repo instructions first: nearest
AGENTS.md, plugin manifests, and the target spec or diff. - Gather bounded local evidence using Evidence Commands.
- Apply the relevant contract:
- Spec Preparation: Spec Contract
- Commits: Commit Contract
- Any review: Mode Rules
- Produce the report using Reporting.
Keep generated helpers and local experiments outside SKILL.md unless they are
durable resources the skill must use.
04 同仓库更多 Skills
verify
Verify one bounded change.
handoff
Prepare a bounded handoff.
intent-correlation-analysis
Analyze a bounded IntentCorrelationPacketV1 and propose reviewable links among user inputs, execution slices, change units, commits, artifacts, and validation outcomes. Use when reconstructing why an observed coding-agent change exists or when Studio needs evidence-backed Intent correlation. Do not use for raw transcript summaries, deterministic file-operation collection, or autonomous confirmation of inferred Intent.
better-harness
Use when /better-harness reviews the outer coding-agent Harness for lifecycle controls, repeated work, project feedback, agent assets, session outcomes, repair planning, durable reports, finding-bound fixes, or manual direct fixes. Invoke only via slash command.
generate-harness-dsl
Generate, revise, or review complete Harness as Code `.harness` files when a coding-agent workflow, agent role, skill, tool contract, MCP connection, runtime, or deployment must be compiler-valid and resolvable with `@qoder-ai/harness`.
memory-recap
Create evidence-linked work profiles, diagnose Coding Agent collaboration friction, and recommend concrete improvements from native memories or frozen exports. Use for memory recaps and agent-usage retrospectives, not memory maintenance or session-performance measurement.