Agent skill

Change Traceability Review

by QoderAI in QoderAI/better-harness

A skill your agent uses for change traceability review across specs, commits, PRs, branches, local diffs, and git history, including Spec Preparation, Review Readiness Checks, and Review…

MITAuto-check passedDevelopment

Install Change Traceability Review

skills CLI
$ npx skills add QoderAI/better-harness --skill change-traceability-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install QoderAI/better-harness change-traceability-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/QoderAI/better-harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/change-traceability-review .claude/skills/change-traceability-review && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
change-traceability-review
GitHub stars
2.4k
Token cost
~559 tokens
SKILL.md length
209 words
Files
6 (incl. references)
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses for change traceability review across specs, commits, PRs, branches, local diffs, and git history, including Spec Preparation, Review Readiness Checks, and Review…

  • Works in 5 steps: Identify the mode from the user's… → Read repo instructions first: nearest… → Gather bounded local evidence using… → …
  • Change traceability review across specs
  • SKILL.md covers Modes and Entry and Routing
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Change Traceability Review is an agent skill from QoderAI/better-harness. 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.

Its SKILL.md is about 560 tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `references/commit-contract.md`, `references/evidence-commands.md` and `references/mode-rules.md`).

It sits in Development, covering Commit messages, Retrospectives and Git workflow. The repository describes itself as: An open-source Harness Engineering platform for coding agents—define harnesses as code, run controlled experiments, inspect evidence, and compare outcomes. Turn task evidence… The licence is MIT.

When your agent uses it

  • Change traceability review across specs
  • Including Spec Preparation
  • Review Readiness Checks
  • Review Retrospectives

Example prompts

  • “/change-traceability-review”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Identify the mode from the user's request or the current review surface.
  2. Read repo instructions first: nearest AGENTS.md, plugin manifests, and the
  3. Gather bounded local evidence using Evidence Commands.
  4. Apply the relevant contract
  5. Produce the report using Reporting.

What it can do on your machine

Read from SKILL.md and the folder at commit 34899f3. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Change Traceability Review loads about 559 tokens when it runs, and up to ~2.4k if it reads all its reference files. Until then it costs about 91 tokens; SKILL.md has 209 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~91
When it runs · the whole SKILL.md, loaded when a task matches
~559
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from QoderAI/better-harness at commit 34899f3, republished under its MIT licence (© QoderAI). 209 words, ~559 tokens.

Download SKILL.mdSave it as .claude/skills/change-traceability-review/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
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.

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

  1. Identify the mode from the user's request or the current review surface.
  2. Read repo instructions first: nearest AGENTS.md, plugin manifests, and the target spec or diff.
  3. Gather bounded local evidence using Evidence Commands.
  4. Apply the relevant contract:
  5. Produce the report using Reporting.

Keep generated helpers and local experiments outside SKILL.md unless they are durable resources the skill must use.

© QoderAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (references) in .agents/skills/change-traceability-review of QoderAI/better-harness.

  • SKILL.md
  • references/commit-contract.md
  • references/evidence-commands.md
  • references/mode-rules.md
  • references/reporting.md
  • references/spec-contract.md

Open the folder on GitHubat commit 34899f3

Compare with similar skills

Change Traceability Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Change Traceability Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Change Traceability Review this skillQoderAI/better-harness2.4k—~559Automated safety check: PassMIT
Contextual Commit Messagesyamadashy/repomix29k1 repos~2.7kAutomated safety check: PassMIT
ToolJet Multi-Repo CommitToolJet/ToolJet41k—~1.3kAutomated safety check: PassAGPL-3.0
Git Workflow and Versioningaddyosmani/agent-skills102k2 repos~3.5kAutomated safety check: NotesMIT
React Router Pull Request Creatorremix-run/react-router57k—~2.5kAutomated safety check: PassMIT
Saleor Commit Workflowsaleor/saleor23k—~575Automated safety check: PassBSD-3-Clause

Similar skills

  • Writes Conventional Commits whose bodies carry action lines recording the intent, decisions and constraints behind a change, not only what changed.

    29k GitHub starsUsed in 1 repo~2.7k tokens
    DevelopmentAuto-check passed
  • Commits changes across ToolJet's root repo and its server/ee and frontend/ee submodules, writing messages from the diffs and updating submodule pointers in order.

    41k GitHub stars~1.3k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    102k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes
  • React Router Pull Request Creator

    remix-run/react-router

    Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.

    57k GitHub stars~2.5k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Commits changes in the Saleor codebase and works through pre-commit hook failures from ruff, mypy, the GraphQL schema check and the migrations check.

    23k GitHub stars~575 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Emoji Commit Conventions

    baptisteArno/typebot.io

    Sets the repository's convention for commit messages and pull request titles: one emoji prefix for the main intent, a concise title and clean follow-up commits.

    11k GitHub stars~424 tokensUpdated yesterday
    DevelopmentAuto-check passed

More from QoderAI/better-harness

All 11 skills in this repo
  • Intent Correlation Analysis

    QoderAI/better-harness

    Analyze a bounded IntentCorrelationPacketV1 and propose reviewable links among user inputs, execution slices, change units, commits, artifacts, and validation outcomes.

    2.4k GitHub stars~1.2k tokensUpdated 9 days ago
    Auto-check passed
  • Better Harness

    QoderAI/better-harness

    A skill your agent uses when /better-harness reviews the outer coding-agent Harness for lifecycle controls, repeated work, project feedback, agent assets, session outcomes, repair planning, durable…

    2.4k GitHub stars~3k tokensUpdated 9 days ago
    Auto-check passed
  • Generate Harness Dsl

    QoderAI/better-harness

    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…

    2.4k GitHub stars~761 tokensUpdated 9 days ago
    Auto-check passed
  • Harness Skill Creator

    QoderAI/better-harness

    A skill your agent uses when bootstrapping or tightening the smallest harness-oriented skill from an existing repository, workflow, evaluation corpus, or harness-analysis chain.

    2.4k GitHub stars~844 tokensUpdated 9 days ago
    Auto-check passed
  • Skill Review

    QoderAI/better-harness

    A skill your agent uses when reviewing Codex, Qoder, or repo-local skills and their prompt chains for trigger quality, workflow clarity, progressive disclosure, duplicated instructions, template…

    2.4k GitHub stars~802 tokensUpdated 9 days ago
    Auto-check passed
  • Diagnose Backend Bug

    QoderAI/better-harness

    Diagnose a bounded backend or multi-service failure from GitHub Issues, Jira, Aone, user-provided exports, logs, traces, responses, stack traces, or job records.

    2.4k GitHub stars~1.2k tokensUpdated 9 days ago
    Auto-check passed

Questions about Change Traceability Review

What does Change Traceability Review do?

A skill your agent uses for change traceability review across specs, commits, PRs, branches, local diffs, and git history, including Spec Preparation, Review Readiness Checks, and Review…. Change Traceability Review is an agent skill from QoderAI/better-harness. 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.

When should I use Change Traceability Review?

Change Traceability Review fits situations like: change traceability review across specs; including Spec Preparation; review Readiness Checks; review Retrospectives.

How do I install Change Traceability Review in Claude Code?

Run `npx skills add QoderAI/better-harness --skill change-traceability-review -a claude-code`. Or copy the skill folder (.agents/skills/change-traceability-review in QoderAI/better-harness) into .claude/skills/change-traceability-review in your project. Claude Code loads it when a task matches its description.

How do I install Change Traceability Review in Codex?

Run `npx skills add QoderAI/better-harness --skill change-traceability-review -a codex`. Or copy the skill folder (.agents/skills/change-traceability-review in QoderAI/better-harness) into .agents/skills/change-traceability-review in your project. Codex loads it when a task matches its description.

Can I use Change Traceability Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add QoderAI/better-harness --skill change-traceability-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/change-traceability-review, .gemini/skills/change-traceability-review, .github/skills/change-traceability-review and .opencode/skills/change-traceability-review in your project.

What does Change Traceability Review need to run?

SKILL.md names no scripts, command-line tools or credentials: Change Traceability Review is instructions for the agent only.

Does Change Traceability Review access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Change Traceability Review safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Change Traceability Review use?

Change Traceability Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Change Traceability Review use?

About 559 tokens (SKILL.md is roughly 2.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.9k tokens, read only when the agent opens those files.

What are the alternatives to Change Traceability Review?

Skills that share tags, products or a category with Change Traceability Review: Contextual Commit Messages (yamadashy/repomix, 29k stars), ToolJet Multi-Repo Commit (ToolJet/ToolJet, 41k stars), Git Workflow and Versioning (addyosmani/agent-skills, 102k stars) and React Router Pull Request Creator (remix-run/react-router, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Change Traceability Review?

QoderAI (a GitHub organization) maintains it in QoderAI/better-harness, which has 2,363 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on September 28, 2026.

Source: QoderAI/better-harness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.