remembering-conversations

barrydobson's avatarfrom barrydobson

Search previous Claude Code conversations for facts, patterns, decisions, and context using semantic or text search

⭐0stars🔀0forks📁View on GitHub🕐Updated Dec 2, 2025

When & Why to Use This Skill

This Claude skill provides a robust search mechanism for historical Claude Code conversations, utilizing both semantic vector similarity and exact text matching. It enables developers and AI agents to efficiently retrieve past facts, architectural decisions, and debugging patterns, significantly enhancing long-term context awareness and preventing the redundant reinvention of existing solutions.

Use Cases

  • Case 1: Debugging recurring issues by searching for similar error messages and their previously discussed resolutions in past sessions.
  • Case 2: Retrieving specific architectural decisions or design patterns established in earlier work to ensure technical consistency.
  • Case 3: Finding specific technical metadata, such as Git SHAs, commit hashes, or configuration snippets mentioned in previous developer-agent exchanges.
  • Case 4: Reducing context window overhead by searching archives for specific context instead of re-explaining complex project history to the agent.
nameRemembering Conversations
descriptionSearch previous Claude Code conversations for facts, patterns, decisions, and context using semantic or text search
when_to_useWhen your human partner mentions "we discussed this before". When debugging similar issues. When looking for architectural decisions or code patterns from past work. Before reinventing solutions. When you need to find a specific git SHA or error message.
version1.0.0

Remembering Conversations

Search archived conversations using semantic similarity or exact text matching.

Core principle: Search before reinventing.

Announce: "I'm searching previous conversations for [topic]."

Setup: See INDEXING.md

When to Use

Search when:

  • Your human partner mentions "we discussed this before"
  • Debugging similar issues
  • Looking for architectural decisions or patterns
  • Before implementing something familiar

Don't search when:

  • Info in current conversation
  • Question about current codebase (use Grep/Read)

In-Session Use

Always use subagents (50-100x context savings). See skills/getting-started for workflow.

Manual/CLI use: Direct search (below) for humans outside Claude Code sessions.

Direct Search (Manual/CLI)

Tool: ~/.claude/skills/collaboration/remembering-conversations/tool/search-conversations

Modes:

search-conversations "query"              # Vector similarity (default)
search-conversations --text "exact"       # Exact string match
search-conversations --both "query"       # Both modes

Flags:

--after YYYY-MM-DD    # Filter by date
--before YYYY-MM-DD   # Filter by date
--limit N             # Max results (default: 10)
--help                # Full usage

Examples:

# Semantic search
search-conversations "React Router authentication errors"

# Find git SHA
search-conversations --text "a1b2c3d4"

# Time range
search-conversations --after 2025-09-01 "refactoring"

Returns: project, date, conversation summary, matched exchange, similarity %, file path.

For details: Run search-conversations --help