memory-audit

To consolidate duplicate memory files, this audit merges redundant entries, prunes dated or irrelevant memories, and sharpens durable takeaways for long-term reuse. It applies staleness, size, and duplicate rules to tidy your project's MEMORY.md index.

The best way to prune stale entries and fix relative time references is to run a memory audit enforcing staleness and time reference rules. It retires dated memories and provides guided actions to delete, resize, drop, or merge flagged files.

Yes, you can identify promotion candidates for a global CLAUDE.md file by running a cross-project sweep. After auditing the current project, the sweep surfaces organization improvements and durable entries suitable for global reuse.

To flag and relocate oversized memory files, the audit checks file sizes against enforced rules and flags them for review. It provides guided actions to resize or relocate bloated files to plans or global docs, improving loading performance and re-findability.

You should avoid an automated memory file cleanup workflow when your project lacks an established MEMORY.md index or memory files to audit. The workflow targets existing projects needing cross-project sweeps, staleness enforcement, and duplicate consolidation.