From ck
Read-only drift detector that diffs SPEC.md against current code and reports violations grouped by severity. Triggers on 'check drift', 'audit the spec', or 'spec vs code'.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ck:checkThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Pure diagnostic. Reports violations. Writes nothing. User decides remedy.
Pure 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.
npx claudepluginhub mvandermeulen/cavekit2plugins reuse this skill
First indexed Jun 18, 2026
Read-only drift detector that diffs SPEC.md against current code and reports violations grouped by severity. Triggers on 'check drift', 'audit the spec', or 'spec vs code'.
Verifies implementation completion by running tests, code hygiene review, spec compliance validation, and drift checks; blocks claims on failures. Use before commits or merges.
Detects contradictions between documentation and code, ambiguous specs, and policy violations across codebases. Produces actionable incoherence report with resolution workflow for consistency audits.