cabinet-record-keeper

To detect documentation drift, you can audit CLAUDE.md files, memory state, and system-status docs against the live codebase. This skill cross-references documented conventions with actual code to flag discrepancies and ensure documentation reflects current reality.

Documentation drift occurs when project docs, schemas, and code comments diverge from the live codebase. It matters because stale documentation misleads users and degrades system behavior, causing Claude sessions to boot with incorrect context during audits or debriefs.

You verify CLAUDE.md accuracy by running an audit pass that cross-references the file's documented conventions and schemas against the actual codebase. The skill checks version alignment with configuration files and inline code comments to enforce conformance.

Yes, you can use this for project onboarding, debrief cycles, and ongoing maintenance. The skill applies documentation validation across the project lifecycle, reconciling findings during debrief to keep memory and system-status in sync with reality.

The best way to keep system-status docs in sync is through guided debriefs that reconcile audit findings. This skill enforces checks on documentation accuracy, drift detection, and version alignment to ensure status docs match the live codebase.

Project documentation fails to match live configuration files due to documentation drift. This skill identifies these discrepancies by enforcing version alignment checks between documented conventions, configuration files, and inline code comments against the actual codebase.