Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fedoroff-vlad/check-drift
Use after ANY change and before opening a PR to verify every coupled artifact moved together. Fires on: changed an env var / port / endpoint / MCP tool / dependency / LLM model / DB schema; "did I update everything"; "check drift"; "reconcile the docs". Reads the repo's .skills/change-map.yaml and reports which coupled files did NOT move.
Passed 3 of 9 test cases with the skill, and 2 of 9 without it.
3 fixed4 passed either way14 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
I edited `pkg/errors/codes.go`. The mapping rule defines `pkg/errors/*.go` as a trigger path leading to `docs/error-codes.md`. Perform the drift check.
| Checked | Without skill | With skill |
|---|---|---|
| Evaluates trigger paths against changed files in the diff to detect fired couplings | Missed | Passed |
The instructions your model reads when the skill loads.
A change is silent drift until the same PR updates all its coupled artifacts. This skill turns that discipline into a check.
.skills/change-map.yaml at the repo root. It lists
couplings, each with a trigger, an optional ssot, a must_update list,
and optional revalidate steps.ssot or trigger-owned file
appears in the diff, treat it as fired.must_update path that
is NOT in the diff. That list is the drift. Be specific — path by path.scripts/check-consistency.sh), run it and fold its output in — it
catches the grep-able stale refs; this skill catches the rest.revalidate steps (a golden
lane, a rebuild), remind the user to run them — a moved file can still be
semantically stale.tools/agent-skills/ pointer + index block exist
and match across the project's docs (this skill's own wiring is a coupling).A short verdict: OK — all couplings satisfied, or a per-coupling list of
missing artifacts. No prose padding. If nothing in the diff matches any
coupling, say so plainly rather than inventing findings.
When a new mechanically-checkable coupling appears, add it to
.skills/change-map.yaml (not to this body) — that is how the "automat" grows
without editing the skill.
test cases passed, vs 2 / 9 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.