← ClaudeAtlas

siftlisted

Review and prune Claude Code's auto-memory entries with the user, moving standing rules into CLAUDE.md. Use when the user asks to clean up, prune, review, or audit memory, or when better-memory says instructions wait for review.
xobotyi/cc-foundry · ★ 23 · AI & Automation · score 81
Install: claude install-skill xobotyi/cc-foundry
**Memory holds facts that stay true after the session that wrote them; rules on how to work belong in a CLAUDE.md the user approved.** An entry kept by mistake steers every later session, while one removed by mistake costs a rediscovery, so removal is the safe error. The user is present for this pass, and their answer is the evidence nothing else can give. ## Where things are - The memory directory is the path the auto-memory section of the system prompt names. better-memory keeps its data in a sibling directory, never inside it: for `<dir>/memory/`, the review file is `<dir>/better-memory/review.md`. That file holds instructions from entries written before better-memory, already moved out of memory and waiting for the user. - **With `mcp__better-memory__remove_entry` in the tool list, better-memory guards the directory.** Remove an entry only with that tool, and save one only with `mcp__better-memory__write_entry`. Write, Edit, and shell commands that change the directory are refused, and better-memory writes `MEMORY.md` itself. - **Without it, the entries are plain files.** `MEMORY.md` is their index, one line per entry: delete an entry file and its line together. ## Phase 1 — Inventory Read every entry file, `MEMORY.md`, `better-memory/review.md` when it exists, and the instruction files in force: the project's `CLAUDE.md`, `.claude/CLAUDE.md`, `CLAUDE.local.md`, its `.claude/rules/` files, `~/.claude/CLAUDE.md`, and the `~/.claude/rules/` files. ## Phase 2