review-memory

Memory Review Protocol

Reviews the auto-memory system that persists across Claude Code conversations. Scope for this project:

~/.claude/projects/<your-project-slug>/memory/
├── MEMORY.md          (index, always loaded into context — lines after 200 are truncated)
└── *.md               (individual memory files, loaded on demand)

Part of the review-* skill family. Cites ../_shared/review-checklist.md.

Owner: docs-manager agent.

When to invoke

• MEMORY.md approaching 200 lines (truncation risk)
• After multiple sessions create new memories without pruning
• Quarterly audit
• When memories start feeling stale or duplicated

Output contract

Board tasks only. Lean summary to main agent.

---

Step 1 — Inventory

• Read ~/.claude/projects/<your-project-slug>/memory/MEMORY.md — record line count, every - [Title](file.md) — hook entry
• Glob every *.md in that directory (excluding MEMORY.md)
• For each memory file, parse frontmatter: name, description, type (user/feedback/project/reference)
• Record body length and last-modified time

Step 2 — Index integrity

For MEMORY.md:

• Line count < 200 (lines after 200 are truncated out of context — critical)
• Every *.md memory file referenced? (orphaned memory files are dead)
• Every - [link](file.md) resolves?
• Every entry has a one-line hook < 150 chars?
• No duplicate entries?
• Organized semantically (not chronologically)?

Step 3 — Frontmatter validation

For each memory file:

Issue	Severity
Missing frontmatter	high
type missing or invalid (must be user/feedback/project/reference)	high
name missing	medium
description missing or generic	medium
Body doesn't match declared type	high

Type correctness

• user — user role, preferences, responsibilities, knowledge
• feedback — guidance given by user, with Why: + How to apply:
• project — ongoing work, goals, initiatives, with Why: + How to apply:
• reference — pointers to external systems