doc-audit

To check for documentation drift, you can audit project documentation against actual source code to identify discrepancies in dependencies, architectural patterns, and rule compliance across multi-app or single-app repositories.

The best way to keep AGENTS.md and CLAUDE.md files in sync is by performing a comprehensive audit that validates instruction files against recent git history and code patterns to detect outdated architectural changes.

You can verify code compliance by scanning the codebase to ensure it adheres to the mandatory rules and prohibitions defined in your project's instruction files, validating that development rules are actively enforced.

Yes, you can audit dependencies in a multi-app repository structure. The audit compares actual project dependencies against documentation to identify missing or obsolete libraries across both multi-app and single-app setups.

Automated architectural pattern analysis scans recent git history and code patterns to ensure new architectural changes are reflected in project docs, maintaining high-fidelity project context for AI agents.

You should run a documentation audit before a major release to ensure that your AGENTS.md and CLAUDE.md files accurately describe the current state of your codebase, dependency lists, and development rules.