← ClaudeAtlas

chronicle-context-retrieverlisted

Search and retrieve context from past development sessions using Chronicle data. Works with MCP (fast, structured) or CLI commands (portable). Use when user asks about previous work, wants to recall past decisions, needs to understand codebase history, or wants to avoid repeating past approaches.
aiskillstore/marketplace · ★ 329 · AI & Automation · score 79
Install: claude install-skill aiskillstore/marketplace
# Chronicle Context Retriever This skill helps you search and retrieve context from past development sessions using Chronicle's database. Works with both MCP server (fast, structured JSON) or CLI commands (portable, everywhere). ## Auto-Activation > **This skill auto-activates!** (Milestone #13) > > Prompts like "how did I implement auth?" or "what did I do yesterday?" automatically trigger this skill. No manual loading needed! > > **Trigger patterns:** how did I, what did I do, find sessions about, search past work > **See:** `docs/HOOKS.md` for full details ## When to Use This Skill Use this skill when: - User asks "what did I do yesterday/last week?" - Need to recall how a feature was implemented - Want to understand why a decision was made - Looking for similar past work or patterns - Avoiding repeating past mistakes or approaches - Need context before starting related work ## How It Works **Option 1: With MCP (Preferred)** 1. **Parse User Query** - Understand what context is needed 2. **Search Chronicle** - `mcp__chronicle__search_sessions()` returns structured JSON (fast!) 3. **Get Details** - `mcp__chronicle__get_session_summary()` for full summaries 4. **Extract Information** - Parse JSON for decisions, blockers, solutions 5. **Present Context** - Summarize findings with session IDs **Option 2: With CLI (Portable)** 1. **Parse User Query** - Understand what context is needed 2. **Search Chronicle** - `chronicle search "keywords"` returns formatted output 3. **