← ClaudeAtlas

mem-historylisted

Query project history, past decisions, and known gotchas from configured memory, local docs, and git history. Use when user asks "last session", "did we already", "what did we decide", "project history", "timeline", or "what happened with".
alexei-led/cc-thingz · ★ 33 · Code & Development · score 85
Install: claude install-skill alexei-led/cc-thingz
# Project Memory Search Query cross-session history via claude-mem. ## Scope Searches observations stored by claude-mem in the current project only. Does not access git history, file contents, or observations from other projects. See also `learning-patterns` for encoding new observations. ## If claude-mem Tools Are Not Available Tell the user that cross-session memory requires the claude-mem plugin (`/plugin install claude-mem@thedotmack`). Suggest alternatives: check `git log` for recent changes, read CLAUDE.md files for project context, or use `git blame` for file history. ## 3-Layer Workflow 1. **Search** (index): `search` with keywords — returns compact list with IDs (~50-100 tokens/result) 2. **Get details**: `get_observations` with IDs from search — returns full narratives (~500-1000 tokens/result) 3. **Timeline**: `timeline` with anchor ID or query — shows chronological context around an observation ## When to Use - **"What did we fix last session?"** — `search` with file path or feature name - **"Did we try this before?"** — `search` with approach keywords - **Past decisions on a feature** — `search` → `get_observations` on relevant IDs - **Recurring bug investigation** — `search` type filter for gotchas/problem-solution - **Full project timeline** — `timeline` with broad query ## Search Tips - Use FTS5 syntax: `AND`, `OR`, `NOT`, quoted phrases - Filter by type: `gotcha`, `problem-solution`, `decision`, `discovery` - Filter by file path for file-specific