| name | remember |
| description | Review auto-memory entries and promote useful ones to CLAUDE.md or project memory files |
| when_to_use | When the user wants to review, organise, or promote their auto-memory entries. Also useful for cleaning up outdated or conflicting entries. |
| argument-hint | optional: focus area or specific memory type to review |
| context | inline |
| allowed-tools | ["read_file","write_file","file_edit","glob"] |
Review all memory layers and propose promotions or cleanups.
$ARGUMENTS
Step 1: Gather all memory layers
Read the following sources (skip if absent):
CLAUDE.md in the project root — project-wide conventions for all contributors.
.claude/memory/MEMORY.md — the memory index.
- All
*.md files in .claude/memory/ — individual memory entries.
Step 2: Classify each auto-memory entry
For every entry in .claude/memory/, determine its best destination:
| Destination | Criteria |
|---|
| CLAUDE.md | Project conventions relevant to all contributors (coding style, architecture decisions, build commands) |
| Keep in memory | Personal preferences, session context, working notes that are still relevant |
| Delete | Outdated facts, superseded decisions, duplicate of CLAUDE.md content, no longer relevant |
Step 3: Identify cleanup opportunities
- Duplicates: two entries that say essentially the same thing → keep the clearer one.
- Outdated: references to removed files, old API versions, resolved bugs.
- Conflicts: two entries that contradict each other → resolve or flag for user.
- CLAUDE.md overlap: memory entry that duplicates content already in CLAUDE.md → delete the memory entry.
Step 4: Present the report
Structure the report as four sections:
Promotions to CLAUDE.md
List entries that should be moved to CLAUDE.md. For each:
- Current memory file name
- Proposed CLAUDE.md section
- Exact text to add
Cleanup (delete or update)
List entries to remove or correct. For each:
- File name and reason (outdated / duplicate / conflict)
- Proposed action
Ambiguous — needs user input
List entries where the right action is unclear. For each:
- File name
- The question to ask the user
No action needed
List entries that are fine as-is.
Step 5: Apply approved changes
After presenting the report, ask the user which actions to apply, then:
- Append approved promotions to
CLAUDE.md under the appropriate section.
- Delete or update memory files as directed.
- Update
MEMORY.md index to reflect removed entries.