Terminal
Terminal/Skill
Compares SPEC.md against your code without writing anything and reports where the code drifts from the spec, grouped by severity.
By Julius Brussee
Works with
npx skills add juliusbrussee/cavekit --skill checkPure diagnostic. Reports violations. Writes nothing. User decides remedy.
Spec drifting silently from code is the #1 SDD failure mode. check is the
detector. Run it after each /build and before each ship — drift caught here is
a diff; drift caught in prod is a §B.
SPEC.md. If missing → "no spec, nothing to check." Stop.§V → check invariants only (default)§I → check interfaces§T → audit task status vs code--all → all threeFor each V:
For each I item:
For each T:
x: verify claimed work present.~: note as in-progress..: note as pending.x rows with no evidence as STALE.Caveman. Grouped by severity.
## §V drift
V2 VIOLATE: auth/mw.go:47 uses `<` not `≤`. see §B.1.
V5 UNVERIFIABLE: no test covers ∀ req path.
## §I drift
I.api DRIFT: POST /x returns `{result}` not `{id}`. route.go:112.
I.cmd MISSING: `foo bar` absent from cli/*.go.
## §T drift
T3 STALE: status `x`, no middleware file exists.
## summary
2 violate. 1 missing. 1 stale. 1 unverifiable.
next: spec skill with `bug:` or fix code at cited lines.
End report with one-line hint per class:
bug: <V.n> or fix code.§T.n if task exists; else spec skill amend §T.amend §T to uncheck.amend §I to document, or delete code.Never invoke fixes. Report only.