Is your documentation still true? Checks the context files your coding agent reads against the code. Five high-precision checks, two reports, zero dependencies.
-
Updated
Sep 7, 2026 - JavaScript
Is your documentation still true? Checks the context files your coding agent reads against the code. Five high-precision checks, two reports, zero dependencies.
Detect stale project docs and keep AI coding agents on current context. Agent skill + dependency-free Python CLI.
Finds documentation that no longer matches your code. Deterministic AST check for pull requests; no API key. TypeScript, JavaScript, Python.
Find the sentences in your docs that stopped being true. docsync binds documentation to the code, config and facts it describes, and `ds check` names every sentence whose code changed, moved or vanished, with the diff and the fix. Go CLI and library, MCP server for AI coding agents, LSP, GitHub Action, Hugo and Docusaurus.
Keeps documentation honest with the code it describes — four axes, one creed, prove it or drop it: a ride-along reflex flags drift, winnow certifies every claim in a deep pass, flourish crafts ugly-but-true docs to a gold standard, cultivate keeps the repo clean, and seed writes code-backed docs where none exist, only with the owner's approval.
Fail CI when numbers in your README drift: test counts, case counts, versions, pinned action tags. A .claims.json checked against real commands and files.
To associate your repository with the stale-docs topic, visit your repo's landing page and select "manage topics."