Docs Guard

Documentation drift is one of those silent killers in codebases, where the README still references a function you renamed three months ago and the getting started guide has broken imports. This skill runs as a verification pass after docs are written or changed. It checks every function name, flag, endpoint, and code sample against the actual source code, not what the model thinks the code probably looks like. The core insight is good: AI generates confident documentation whether or not the API exists. Use it reactively after a writing pass, not as a live editor. The rules are opinionated but grounded in real drift patterns, like demanding that performance claims point to actual benchmarks in the repo.