ce:compound-refresh

To keep documentation accurate after a codebase refactor, audit your pattern docs against the current codebase to detect drift, update stale references, or archive outdated guidance automatically. This ensures technical learnings reflect recent structural changes and dependency upgrades.

Detecting drift in pattern docs involves auditing your solutions directory against the current codebase to identify outdated guidance. The process reviews existing learnings, flags contradictions from recently solved problems, and determines whether to update or archive the documentation.

Automate the maintenance of outdated codebase learnings by running an audit that operates in interactive or autonomous modes. The autonomous mode applies safe actions like archiving stale docs, while the interactive mode asks questions before updating references or replacing guidance.

You should audit your solutions documentation for accuracy after dependency upgrades, migrations, or refactors. Additionally, review these docs when a recently solved problem contradicts an existing learning, or when pattern docs no longer reflect the current code structure.

Yes, you can run automated documentation updates without manual review using autonomous mode, which applies safe actions directly to outdated learnings. It produces a final report with Applied and Recommended sections so you can verify which changes were executed automatically.