doc__guard-drift

Detect documentation drift by comparing repository docs to primary source artifacts like code, schemas, and configs. The audit treats docs as testable claims, verifying them against implementation files to surface mismatches and generate evidence-backed drift reports with precise file references.

Audit API docs for accuracy during PR reviews by validating them against source-of-truth contracts and implementation files. The audit identifies mismatches between documented endpoints and actual code, generating concrete drift reports with suggested fixes to maintain documentation truthfulness.

Fix outdated runbooks and architecture notes after refactoring by running a documentation audit across the repository. The audit compares docs to recent changes, deployment files, and tests, then reports mismatches with exact file references and recommended corrections to snap docs back to reality.

Verify documentation claims against schemas, tests, and deployment configs by running an audit that treats docs as testable assertions. The audit checks README, API docs, and runbooks against these primary source artifacts to surface mismatches and missing coverage with evidence-backed reports.

Run a documentation drift audit before releases, during PR reviews, or after refactors to catch mismatches between docs and implementation. The audit validates docs against current repository artifacts, ensuring documentation accuracy and preventing outdated information from reaching users.

A documentation drift report includes evidence-backed mismatches with precise file references and recommended fixes. The audit compares docs to code, schemas, tests, and configs, generating concrete corrections that snap documentation back to reality with source-of-truth validation.