/si:review — Analyze Auto-Memory

Domain: Engineering - Core | Skill: review | Source: engineering-team/self-improving-agent/skills/review/SKILL.md

---

/si:review — Analyze Auto-Memory

Performs a comprehensive audit of Claude Code's auto-memory and produces actionable recommendations.

Usage

/si:review                    # Full review
/si:review --quick            # Summary only (counts + top 3 candidates)
/si:review --stale            # Focus on stale/outdated entries
/si:review --candidates       # Show only promotion candidates

What It Does

Step 1: Locate memory directory

# Find the project's auto-memory directory
MEMORY_DIR="$HOME/.claude/projects/$(pwd | sed 's|/|%2F|g; s|%2F|/|; s|^/||')/memory"

# Fallback: check common path patterns
# ~/.claude/projects/<user>/<project>/memory/
# ~/.claude/projects/<absolute-path>/memory/

# List all memory files
ls -la "$MEMORY_DIR"/

If memory directory doesn't exist, report that auto-memory may be disabled. Suggest checking with /memory.

Step 2: Read and analyze MEMORY.md

Read the full MEMORY.md file. Count lines and check against the 200-line startup limit.

Analyze each entry for:

1. Recurrence indicators
2. Same concept appears multiple times (different wording)
3. References to "again" or "still" or "keeps happening"

4. Similar entries across topic files

5. Staleness indicators

6. References files that no longer exist (find to verify)
7. Mentions outdated tools, versions, or commands

8. Contradicts current CLAUDE.md rules

9. Consolidation opportunities

10. Multiple entries about the same topic (e.g., three lines about testing)

11. Entries that could merge into one concise rule

12. Promotion candidates — entries that meet ALL criteria:

13. Appeared in 2+ sessions (check wording patterns)
14. Not project-specific trivia (broadly useful)
15. Actionable (can be written as a concrete rule)
16. Not already in CLAUDE.md or .claude/rules/

Step 3: Read topic files

If MEMORY.md references or the directory contains additional files (debugging.md, patterns.md, etc.): - Read each one - Cross-reference with MEMORY.md for duplicates - Check for entries that belong in the main file (high value) vs. topic files (details)

Step 4: Cross-reference with CLAUDE.md

Read the project's CLAUDE.md (if it exists) and compare: - Are there MEMORY.md entries that duplicate CLAUDE.md rules? (→ remove from memory) - Are there MEMORY.md entries that contradict CLAUDE.md? (→ flag conflict) - Are there MEMORY.md patterns not yet in CLAUDE.md that should be? (→ promotion candidate)

Also check .claude/rules/ directory for existing scoped rules.

Step 5: Generate report

Output format:

📊 Auto-Memory Review

Memory Health:
  MEMORY.md:        {{lines}}/200 lines ({{percent}}%)
  Topic files:      {{count}} ({{names}})
  CLAUDE.md:        {{lines}} lines
  Rules:            {{count}} files in .claude/rules/

🎯 Promotion Candidates ({{count}}):
  1. "{{pattern}}" — seen {{n}}x, applies broadly
     → Suggest: {{target}} (CLAUDE.md / .claude/rules/{{name}}.md)
  2. ...

🗑️ Stale Entries ({{count}}):
  1. Line {{n}}: "{{entry}}" — {{reason}}
  2. ...

🔄 Consolidation ({{count}} groups):
  1. Lines {{a}}, {{b}}, {{c}} all about {{topic}} → merge into 1 entry
  2. ...

⚠️ Conflicts ({{count}}):
  1. MEMORY.md line {{n}} contradicts CLAUDE.md: {{detail}}

💡 Recommendations:
  - {{actionable suggestion}}
  - {{actionable suggestion}}

When to Use

• After completing a major feature or debugging session
• When /si:status shows MEMORY.md is over 150 lines
• Weekly during active development
• Before starting a new project phase
• After onboarding a new team member (review what Claude learned)

Tips

• Run /si:review --quick frequently (low overhead)
• Full review is most valuable when MEMORY.md is getting crowded
• Act on promotion candidates promptly — they're proven patterns
• Don't hesitate to delete stale entries — auto-memory will re-learn if needed