← ClaudeAtlas

ccc-recalllisted

Search across all past Claude Code sessions — find when you solved a similar problem, what decision you made last quarter, which file you were editing the day before…
KevinZai/commander · ★ 3 · AI & Automation · score 79
Install: claude install-skill KevinZai/commander
# /ccc-recall — Cross-Session Memory Search Your past sessions are a goldmine. This skill indexes it. > **Optional integration:** If you have `claude-mem` (a separate AGPL-licensed > tool by @thedotmack) installed via `npm install claude-mem`, `/ccc-recall` > will use it for vector search across sessions. **CC Commander does NOT > bundle claude-mem** — install separately or skip; CCC's built-in grep + > file-based recall works without it. ## When to use - "Didn't we solve this last month?" — search instead of re-solving - "What did I decide about {auth provider / db vendor / testing lib}?" — pull the decision - "When did {bug} first appear?" — find the session it landed in - "Which file had that specific comment about the edge case?" — grep across sessions ## Not for - Current session state — that's `/ccc-memory` (curated) or `/ccc-save-session` (snapshot) - Code search across the repo — use `Grep` tool directly - Documentation lookup — use `context7` MCP or `/ccc-docs` ## Three-layer lookup Run them in order of fastest-first: ### Layer 1 — Session transcripts (`~/.claude/sessions/*.tmp`) File-based. Fast grep: ```bash grep -l "${keyword}" ~/.claude/sessions/*.tmp | head -5 ``` Returns session files whose summary mentions the keyword. Each is a structured save from `/ccc-save-session` with sections for What Worked / Didn't Work / Decisions. ### Layer 2 — `memory/` curated notes If project has a `memory/` dir (from `/ccc-memory`): ```bash grep -rn "${keyword}" memo