---

name: session-search description: Search past conversations by keywords, timeframe, or ID. Triggers on "search sessions", "find that conversation", "what did we work on", "look up past discussion about X", "where were we", "what did I learn", "knowledge gaps", "retrospective". Also trigger on: "what did we discuss...", "you mentioned...", past tense verbs referring to prior work, possessives without context ("my project", "my auth system"), and assumptive questions that reference unshared context. Extracts clean conversation data and applies analytical lenses for structured insights.

session-search

Extraction

python3 ~/.claude/skills/session-search/scripts/extract_conversations.py --days 3

Option	Effect
--days N	Days from last activity (not today)
--from-today	Days from today instead
--all-projects	Cross-project (implies --from-today)
--project /path	Filter to specific project
--compact	No metadata, more conversation
--min-exchanges N	Skip sessions with < N exchanges
--ids abc,def	Fetch specific conversations
--paths /path.jsonl	Direct file paths

Output: Default shows files, tools, errors + conversation. --compact omits metadata.

Time modes: --days N counts from last activity (useful when returning to old projects). --all-projects or --from-today counts from today (calendar-based).

Workflow

1. Grep for keywords (generate semantic synonyms):

   grep -l -E "auth|login|session" ~/.claude/projects/*/*.jsonl
   

2. Extract: python3 ... --paths /found/conv.jsonl

3. Apply lens using parameters and questions below.

---

Lenses

Routing

User Says	Lens
"where were we", "recap"	restore-context
"what I learned", "reflect"	extract-learnings
"gaps", "struggling"	find-gaps
"mentor", "review process"	review-process
"retro", "project review"	run-retro
"decisions", "CLAUDE.md"	extract-decisions
"bad habits", "antipatterns"	find-antipatterns

Parameters

Lens	Days	Flags	Also Gather
restore-context	3	—	git status, git log -10
extract-learnings	14	--all-projects --compact	—
find-gaps	30	--all-projects --compact	—
review-process	14	--all-projects --compact	recent git log
run-retro	30	--project /path	full git history
extract-decisions	90	--project /path	—
find-antipatterns	30	--all-projects --compact	—

--min-exchanges 2 or 3 filters out short sessions and reduces noise.

Core Questions

Lens	Ask
restore-context	What's unfinished? What were the next steps?
extract-learnings	Where did understanding shift? What mistakes became lessons?
find-gaps	What topics recur? Where is guidance needed repeatedly?
review-process	Is there planning before coding? Is debugging systematic?
run-retro	How did the solution evolve? What worked? What was painful?
extract-decisions	What trade-offs were discussed? What was rejected and why?
find-antipatterns	What mistakes repeat? What confusions persist?

Follow-ups: find-gaps → suggest learn-anything. extract-decisions → suggest /updateclaudemd.

Grep Signals

Use these patterns to find relevant sessions before extracting:

Lens	Grep Pattern
extract-learnings	learned|realized|understand now|clicked|got it
find-gaps	confused|don't understand|struggling|help with
extract-decisions	decided|chose|instead of|trade-off|because
find-antipatterns	again|same mistake|repeated|forgot

---

Synthesis

Principles

1. Prioritize significance — 3-5 key findings, not exhaustive lists
2. Be specific — file paths, dates, project names
3. Make it actionable — every finding suggests a response
4. Show evidence — quotes or references
5. Keep it scannable — clear structure, no walls of text

Structure

## [Analysis Type]: [Scope]

### Summary
[2-3 sentences]

### Findings
[Organized by whatever fits: categories, timeline, severity]

### Patterns
[Cross-cutting observations]

### Recommendations
[Actionable next steps]

Length

Default: 300-500 words. Expand only when data warrants it.