evidence-checklisted

Verify that the evidence ledger's spec-to-code coordinates still resolve — broken links fail, ranges touched since the baseline demand re-verification. Use when: checking ledger health, before merging spec-driven work, wiring the check into CI, or after large refactors. NOT for: judging whether the code is CORRECT — this checks that the evidence still points somewhere, not that the claim is still true.
MichaelYcJo/SpecSeal · ★ 1 · Code & Development · score 67

Install: claude install-skill MichaelYcJo/SpecSeal

# evidence-check — does the ledger still point at what it claims? Specs rot silently: code moves, the ledger's `file:line` coordinates keep claiming grounds that are no longer there, and the next reader trusts them. This skill makes that rot mechanical to catch — the same way a broken test catches a regression. ## Run ```bash evidence-check [ROOT] # on PATH while the plugin is enabled # from a session, simply: evidence-check --strict . ``` | Flag | Meaning | |---|---| | `--ledger GLOB` | ledgers to scan (default `.specseal/map.md`) | | `--default-repo PATH` | migration ledgers cite the ORIGINAL repo with unprefixed paths — resolve them against this checkout | | `--map NAME=PATH` | resolve `NAME/...` prefixed coordinates against another checkout | | `--strict` | drift exits 2, the broken-coordinate code, instead of 1 — it fails the run either way | ## Verdicts and what to do | Verdict | Meaning | Action | |---|---|---| | `BROKEN` (exit 2) | file gone or range beyond file length | fix the coordinate now — a broken ground is worse than none | | `DRIFTED` (exit 1; 2 under `--strict`) | commits since the row's baseline SHA touched the range | re-open the coordinate, re-verify the claim, and write the SHA you verified at into the row's Checked column | | `EXTERNAL` | path resolves in no known checkout | pass `--map`/`--default-repo`, or accept as out of scope | | `OK` | resolves, untouched since its baseline | nothing | Drift is `git diff baseline..HEAD` per cited f