DocDrift
catch stale code references in your docs before they mislead your next AI session
npx -y github:Isco0819/docdriftEver run into this?
Like Vale which has 4k+ GitHub stars for prose linting, but missing code-reference awareness. When AI agents refactor code they rename functions, CLI flags, and env vars without touching the README. Those stale backtick references silently mislead future AI coding sessions and confuse contributors who trust the docs.
The fix
npx CLI and MCP server that parses your markdown docs for inline code references, cross-checks each against the actual source tree, and reports every drift with fuzzy-match rename suggestions — runs pre-commit or as an MCP tool the agent calls before finishing a refactor.
What it does
- extract backtick terms, CLI flag names, and env var keys from any markdown file
- cross-check each reference against your source tree with fuzzy-match suggestions for renames
- MCP tool check_docs(changed_files) lets AI agents self-audit docs before committing a refactor