Conversation search

Skill ajaygunalan/flow-friction/skills/conversation-search

Claude Code skills for researchers, by a researcher. Humans + agents exploring what hasn't been built yet — without losing alignment along the way.

Install

npx -y skills add ajaygunalan/flow-friction --skill conversation-search

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Search past Claude Code conversation history. Use when asked to recall, find, or search for anything from previous conversations - including content discussed, links shared, problems solved, topics covered, things posted, or work done together. Triggers include "what did we do today", "summary of our work", "what did we work on", "from our conversations", "what did we discuss", "which X was about Y", "recall when we", "find where we talked about", "search history", "what did I share/post/send you about", "how did we fix", or any reference to past sessions or collaborative work.

SKILL.md

3.4 KB, as published. Nobody here has run it

Important: Never infer work history from git status alone — always search conversation history.

What is the user looking for?

Determine the query type:

Temporal ("what did we do today?", "summary of this week") → use digest mode
Specific topic ("how did we fix X?", "find where we discussed Y") → use keyword search
Combine date filters with keywords when possible for speed

How do we find it?

Digest Mode (temporal questions)

python3 ~/.claude/skills/conversation-search/scripts/search_history.py --digest today
python3 ~/.claude/skills/conversation-search/scripts/search_history.py --digest yesterday
python3 ~/.claude/skills/conversation-search/scripts/search_history.py --digest 2026-01-04
python3 ~/.claude/skills/conversation-search/scripts/search_history.py --digest today --project ~/Projects/nuxt/secondBrain

Keyword Search (specific topics)

python3 ~/.claude/skills/conversation-search/scripts/search_history.py --today "newsletter"
python3 ~/.claude/skills/conversation-search/scripts/search_history.py --yesterday "bug fix"
python3 ~/.claude/skills/conversation-search/scripts/search_history.py --days 7 "refactor"
python3 ~/.claude/skills/conversation-search/scripts/search_history.py --since 2026-01-01 "feature"
python3 ~/.claude/skills/conversation-search/scripts/search_history.py "EMFILE error"
python3 ~/.claude/skills/conversation-search/scripts/search_history.py "nuxt content" --project ~/Projects/nuxt/secondBrain

Options

Flag	Description
`--project <path>`	Search only a specific project
`--limit <n>`	Maximum results (default: 5)
`--format json\|text`	Output format (default: text)
`--today`	Only sessions from today
`--yesterday`	Only sessions from yesterday
`--days N`	Sessions from last N days
`--since YYYY-MM-DD`	Sessions since date
`--digest [DATE]`	Show daily digest (today, yesterday, or YYYY-MM-DD)

If more detail needed

Read the full JSONL file:

cat ~/.claude/projects/<encoded-path>/<session-id>.jsonl | head -100

What do the results look like?

Digest Mode

## January 04, 2026 - 4 sessions

### 1. Newsletter System Implementation
   Session: `2da9ab0b`
   Branch: `main`
   Files: content.config.ts, NewsletterCard.vue, NewsletterHeader.vue
   Commands: 6 executed

Search Mode

Results include:

Score: Relevance ranking
Problem: The original issue or request
Solution: How it was resolved
Commands Run: Bash commands executed during the fix
Session ID: For locating the full conversation

Tips

Use --digest for temporal questions — much faster than keyword search
Combine date filters with keywords for speed
Use specific technical terms (error messages, tool names)
Try broader terms if specific search fails