Docs drift guardrail for commits and PRs

Catch stale docs
before they hit main.

DocDrift checks changed code against your README, docs, and examples. It flags when the docs are now wrong, incomplete, or missing, then helps fix them before merge.

$pip install docdrift
See the repo
Runs before commit and in PRs
Works with local or cloud AI
Repo-native and open source
docdrift commit

Catches docs drift where it happens

DocDrift looks at staged code changes, maps them to related docs, and flags when the docs are now wrong.

Fits the workflow developers already use

Run it in the CLI before commit, or in GitHub Actions so every PR gets the same check automatically.

Specialized beats generic

General AI agents can update docs when you ask. DocDrift is valuable because it remembers to ask every time.

Why this instead of an agent

Agents can update docs.
DocDrift makes sure someone remembers to.

The real value is not that an LLM can write a paragraph. The real value is that DocDrift checks the same thing every time a repo changes, in the same place your team already reviews code.

CategoryDocDriftGeneral AI agent
Change-awareReads the staged diff and checks only what changedUsually needs a prompt and human context
Workflow-nativeWorks in commits and PR checksUsually lives in chat or the editor
Docs-specificFocused on stale docs, examples, params, returns, and missing docsBroad, but less opinionated and less repeatable
Team consistencyRuns the same way every timeQuality depends on the person asking

API teams

Catch outdated README examples, return values, and exceptions before customers copy the wrong flow.

Open-source maintainers

Keep installation steps, examples, and feature docs aligned with the code people actually pull.

Small engineering teams

Add one guardrail to your workflow instead of asking every engineer to remember docs manually.

GitHub Actions

Same detection logic in the CLI and in PRs

Run DocDrift locally before commit, then enforce the same check on pull requests. The specialized engine stays consistent across both surfaces.

.github/workflows/docdrift.yml
name: DocDrift
on:
  pull_request:
    branches: [main, master]

jobs:
  check-docs:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0

      - uses: ayush698800/docwatcher@v2.1.0
        with:
          groq_api_key: ${{ secrets.GROQ_API_KEY }}

Pricing path

Start free. Charge for private team convenience.

The easiest path to paid usage is keeping the open-source CLI free, then charging teams for private-repo workflows and convenience layers.

Open sourceFree

CLI, local AI, open-source repos, pre-commit hook, and basic GitHub Action use.

Private repo plan$12-$19 / repo

Best path for first 100 paying users: private repos, smoother onboarding, higher fix volume, and team support.

Team plan laterOrg workflow

Add policies, org-wide defaults, PR reporting, and simple admin controls once the core paid path is proven.

Start here

Stop shipping stale docs.

Install DocDrift, run it on one real repo, and use that proof to attract your first users. The product sells best when it prevents a mistake someone almost merged today.

$pip install docdrift
View GitHubInstall package