Doc-audit

Point it at a GitHub repo. It reads the git history and shows which docs pages the code changed underneath, 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.
  3. BoardStale pages and missing docs land on one board.

Open a Real Audit

Recorded 2026-10-10

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