Doc-audit

Point it at any GitHub repo, with or without a docs folder. It reads the whole git history, code and docs. It shows which pages the code left behind, who works on which part of the code, and what to ship next.

Public repos are audited on GitHub Actions in about 2 minutes. The board link lands on the request issue. Agents can read agent.md.

Doc-audit video thumbnail: 15 stale pages found in dbt-core, each fix goes to the person who knows the code

Watch the Doc-audit journey, 1:56Short on time? The 57 s tour

  1. CloneOne blobless clone, on GitHub Actions or on your machine. $0 in model calls.
  2. MatchEach commit is matched to the docs pages on its topic, and to the part of the code it changed.
  3. BoardStale pages, missing docs and the team map of the code land on one board.

Open a Real Audit

Recorded 2026-10-10

    Run your own: 1stRun audit owner/repo. The data lives in docs/audits in the public repo.