docs-freshness-check
Installation
SKILL.md
Docs Freshness Check
Verify that the project's core documentation reflects the current codebase, then fix what has drifted. Documentation that lies is worse than missing documentation — it actively misleads every reader (human and agent) who trusts it.
What "stale" means
A doc is stale when its claims contradict the code. Check each file against these specific failure modes:
| Failure mode | Example |
|---|---|
| Counted wrong | "18 skills" when there are 19; "see foo.go" when it's renamed |
| Points at ghosts | References a file, symbol, command, or path that no longer exists |
| Missing reality | A shipped feature or new file the doc doesn't mention |
| Contradicts code | Doc says X works; code shows X is broken, disabled, or removed |
| Wrong commands | Build/test/run instructions that fail when executed |
| Stale status | Claims a known issue is open when it's fixed (or vice versa) |
A doc is fresh only when you can confirm its concrete claims against the code. "Looks fine" is not a freshness check — open the files it names and verify.