review-memorylisted

# Skill: review-memory ## When to Use Run `/review-memory` when prompted by the memory review hook, or any time you want to audit what auto-memory has captured for this project. Use after completing a milestone, before starting new work, or when memory feels noisy. Do NOT run this mid-task. Finish what you're working on first. ## Mode Selection - **Full mode** (default): Reads all topic files, presents detailed categorisation table, acts on confirmation. - **Compact mode** (`/review-memory --compact`): Quick list of new memories with one-line summaries. Asks "promote, keep, or remove?" for each. No topic file reads. Use when context is low or time is short. --- ## Full Mode ### Step 1: Load Memory Read `MEMORY.md` from the project's memory directory. The path follows this pattern: `~/.claude/projects/<project-path-encoded>/memory/MEMORY.md` Where `<project-path-encoded>` is the project root path with `/` replaced by `-`. Also read any topic files referenced from MEMORY.md (e.g., `feedback_testing.md`, `project_auth.md`). List what was found: - Total entries in MEMORY.md - Topic files and their one-line descriptions - Last modified dates ### Step 2: Categorise Each Entry For each memory entry, evaluate all three categories **in this order**: 1. **Remove?** Is this stale, wrong, duplicated by CLAUDE.md/rules, or derivable from code/git? If yes → Remove. 2. **Promote?** Does this encode a convention, decision, or constraint that should survive memory cleanup? If l