memory-review

Topics in the source

• /si:memory-review — Analyze Auto-Memory
• Usage
• What It Does
• Step 1: Locate memory directory
• Step 2: Read and analyze MEMORY.md
• Step 3: Read topic files
• Step 4: Cross-reference with CLAUDE.md
• Step 5: Generate report

Performs a comprehensive audit of Claude Code's auto-memory and produces actionable recommendations. If memory directory doesn't exist, report that auto-memory may be disabled. Suggest checking with /memory. Read the full MEMORY.md file. Count lines and check against the 200-line startup limit. Analyze each entry for: 1. Recurrence indicators Same concept appears multiple times (different wording) References to "again" or "still" or "keeps happening" Similar entries across topic files 2. Staleness indicators References files that no longer exist (find to verify) Mentions outdated tools, versions, or commands Contradicts current CLAUDE.md rules 3. Consolidation opportunities Multiple entries about the same topic (e.g., three lines about testing) Entries that could merge into one concise rule 4. Promotion candidates — entries that meet ALL criteria: Appeared in 2+ sessions (check wording patterns) Not project-specific trivia (broadly useful) Actionable (can be written as a concrete rule) Not already in CLAUDE.md or .claude/rules/ If MEMORY.md references or the directory contains additional files (debugging.md, patterns.md, etc.): Read each one Cross-reference with MEMORY.md for dupli

This is an excerpt. Refer to the complete source and its current requirements.