Feature: automatic memory review and pruning of redundant entries

Problem

Claude Code's memory system accumulates entries over time, but there is no mechanism to automatically detect and suggest pruning memories that have become redundant — for example, because their content is now covered by:

• Updated skills (.claude/skills/)
• CLAUDE.md files
• Other memories that subsume them

Currently, cleanup is entirely manual: the user must remember to ask Claude to review its memories and cross-reference them against other context sources. This doesn't scale well as the number of memories, skills, and project instructions grows.

Proposed solution

Add a periodic or on-demand memory review mechanism that:

1. Cross-references memory entries against skills, CLAUDE.md, and other memories
2. Identifies redundant or stale entries
3. Suggests pruning them to the user (rather than deleting silently)

This could be triggered automatically (e.g. at conversation start when the memory index is loaded) or via a slash command like /memory-review.

Why this matters

• Redundant memories waste context window tokens
• Contradictions between memories and updated skills/instructions can cause confusion
• Users shouldn't need to manually audit Claude's memory system