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.
npx skills add QoderAI/better-harness --skill change-traceability-review --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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](references/spec-contract.md). - **Review Readiness Check**: inspect the current diff, staged diff, PR text, branch, or selected commits before review/merge. Load [Mode Rules](references/mode-rules.md) and [Reporting](references/reporting.md). - **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](references/mode-rules.md) and [Reporting](references/reporting.md). ## Entry and Routing 1. Identify the mode from the user's request or the curr
- Modes
- Entry and Routing
What does the change-traceability-review skill do?
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.
How do I install it?
Run `npx skills add QoderAI/better-harness --skill change-traceability-review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From QoderAI/better-harness, a repository with 1,619 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.