doc-drift-detectorlisted

# Doc drift detector Documentation goes stale in two ways. Prose gets subtly wrong, which needs a human who knows the product. And **specific, checkable claims stop being true** — a path that moved, a script that was renamed, a flag that was dropped, a minimum version that went up. Only the second kind can be checked mechanically, and it is where most of the damage is, because those are the lines a reader copies and runs. This skill does that kind and says so, rather than producing a general opinion about documentation quality. ## Procedure ### 1. Extract and check the claims `<skill-dir>` is the directory this SKILL.md was loaded from — the skill installs outside your project, so its script is named by full path, never relatively. ``` python3 <skill-dir>/scripts/doc_claims.py README.md # one document python3 <skill-dir>/scripts/doc_claims.py docs/ --recursive # a whole doc set ``` For each document the script extracts four kinds of checkable claim and resolves each against the repository: - **paths** — file and directory references, including those inside code fences - **commands** — `npm run x`, `pnpm y`, `make z`, checked against `package.json` scripts and the `Makefile` - **symbols** — identifiers in inline code that look like exported names - **versions** — declared minimums for runtimes and packages, against the manifests It prints each claim as `OK`, `STALE`, or `UNCHECKABLE`, with the line number. ### 2. Discard the false positives before reporti