Index of every page on this site: llms.txt
All skills
qoderai avatar

/change-traceability-review

@c6240a8
by qoderaiqoderai/better-harness2.5k stars
208
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/qoderai/better-harness/change-traceability-review

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesspec-contract.md

≈461 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Spec-First Contract

For non-trivial behavior, agent, hook, template, API, workflow, or review-flow changes, create or update a spec before implementation. Use docs/specs/<yyyy-mm-dd>-<story-id>-<slug>.md when a Story exists; otherwise use docs/specs/<yyyy-mm-dd>-<slug>.md for justified maintenance, docs-only, test-only, dependency, or infra work. Use the spec's creation date for the prefix and keep that prefix stable across later edits.

Keep the spec small but executable enough for review:

# <Spec title>

## Traceability
- Spec ID: <story-id-or-slug>
- Status: Draft

## Intent
What user, maintainer, or agent outcome changes, and why.

## Acceptance Scenarios
- AC-1: <observable behavior and success criterion>

## Non-goals
Explicit exclusions that prevent speculative expansion.

## Plan and Tasks
Technical approach, affected files/modules, task list, and decision rationale.

## Test and Review Evidence
Commands, expected evidence, manual checks, and risk notes mapped to AC ids.

Keep titles human-readable only. Do not put Story ids, draft, implemented, review state, or other traceability metadata in the title. Do not use YAML front matter for docs/specs/*.md unless a repository-specific parser requires it. Start new Spec Preparation output as Status: Draft; change it to Accepted, Implemented, or Superseded only when visible local evidence supports that state. Add a Story field only when there is a literal Story or issue id.

Use [NEEDS CLARIFICATION: question] for unknowns instead of guessing. A spec with unresolved clarification markers is not ready for implementation unless the user explicitly asks for exploratory work. Keep intent focused on what/why; put how/where in Plan and Tasks. Do not add speculative features without a matching Story, AC id, or explicit user request.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning3mo3 checks · Risk MEDIUM
  • Gen Agent Trust Hub3mo

    The skill helps perform traceability reviews by executing local git and search commands. It is vulnerable to command injection if user-provided identifiers, such as Story IDs, are not properly sanitized before being passed to shell commands. Additionally, the skill processes external content including git logs, diffs, and specification documents which could contain malicious instructions designed to manipulate the agent's behavior through indirect prompt injection.

  • Socket3mo

    No alerts

  • Snyk3mo

    Risk: LOW · No issues

Signed by skilld at c6240a8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 4 months ago

README badge

README badge for qoderai/better-harness/change-traceability-review