Catch documentation drift with a scheduled AI agent

Crongent catches documentation drift by running an agent that reads your docs and the code they describe, then lists every claim that is no longer true: renamed commands, removed env vars, stale setup steps. It opens one issue per repo with exact fixes, so docs stay accurate for people and coding agents.

The problem

Out-of-date docs waste onboarding time and mislead AI coding agents that trust README and CLAUDE.md files.

How to set it up in Crongent

  1. Create a weekly routine scoped to repos with docs.
  2. List the files to check (README.md, docs/, CLAUDE.md).
  3. Allow issue creation only.

Example routine

Name
Docs drift
Trigger
Weekly, Wednesday 10:00
Model
anthropic/claude-sonnet-5.5
Instructions
Compare README.md and CLAUDE.md against package.json scripts, env examples and folder layout. List every false statement with the fix.

Who uses it

Frequently asked questions

Why does doc accuracy matter for AI agents?
Coding agents read README and CLAUDE.md first. A wrong command there gets repeated in every session.

Related use cases