← ClaudeAtlas

claude-memory-capturelisted

Extracts durable patterns from the current session and writes them to `.claude/memory/` as feedback, project, user, or reference memory files. Use when asked to "capture memory", "capture lessons", "wrap up the session", "end of session memory", or as the final step in autoship. Do NOT use to curate existing memory. Use `claude-memory-review` for that.
erclx/toolkit · ★ 1 · AI & Automation · score 74
Install: claude install-skill erclx/toolkit
# Claude memory capture Scan the current session for patterns worth persisting, write them as memory files, and update the index. Pair with `claude-memory-review` for later curation. ## Guards - All `.claude/memory/` reads and writes resolve at the main worktree root, not the current worktree. See Worktrees in `CLAUDE.md`. - If `.claude/memory/` does not exist at the main worktree root, create it. - If the session produced no user corrections, confirmations, or context disclosures worth persisting, stop: `✅ Nothing worth capturing.` ## Step 1: read context Read in parallel from the project root, skipping any that do not exist: - `CLAUDE.md`: Memory section rules, including save thresholds and file format overrides - `.claude/memory/MEMORY.md`: existing index, to avoid duplicates - `standards/prose.md`: prose conventions applied to memory file bodies ## Step 2: classify candidates Scan the session and group candidate patterns into four types: - **feedback**: explicit user corrections, stated preferences, or non-obvious confirmations - **project**: decisions, initiatives, deadlines, or motivations not derivable from git or code - **user**: role, expertise, responsibilities, or working preferences - **reference**: pointers to external systems (dashboards, trackers, channels) Apply the save threshold: a feedback memory only fires on explicit user correction, or on a pattern that repeated twice in the session. First-occurrence slips are noise. Project, user, and referenc