documentation-pass

To prevent documentation drift after major code refactors, you can audit project documents like CLAUDE.md, README files, and ADRs against recent code changes. This process identifies stale guidance and generates a prioritized fix plan before any edits are applied.

The best way to clean up a bloated CLAUDE.md file is to perform a rule-based audit that removes brittle snapshots and mutable enumerations. This ensures the file retains only durable, high-utility workflow rules.

Yes, you can audit architecture decision records (ADRs) against recent code and chat context. The audit inspects the ADR directory to ensure the documentation reflects the true current architecture before proposing any changes.

To update project docs without auto-writing unwanted changes, use a two-phase workflow that produces findings and an explicit apply plan first. This strict no-auto-write behavior ensures changes are applied only after explicit user approval.

You should run a documentation audit after major refactors, architecture decisions, or when CLAUDE.md becomes stale or bloated. This ensures your docs remain current and actionable by checking them against the actual repository state.