Remembering Conversations
Search previous Claude Code conversations for facts, patterns, decisions, and context using semantic or text search
Best use case
Remembering Conversations is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Search previous Claude Code conversations for facts, patterns, decisions, and context using semantic or text search
Teams using Remembering Conversations should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/remembering-conversations/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How Remembering Conversations Compares
| Feature / Agent | Remembering Conversations | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Search previous Claude Code conversations for facts, patterns, decisions, and context using semantic or text search
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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:** ```bash search-conversations "query" # Vector similarity (default) search-conversations --text "exact" # Exact string match search-conversations --both "query" # Both modes ``` **Flags:** ```bash --after YYYY-MM-DD # Filter by date --before YYYY-MM-DD # Filter by date --limit N # Max results (default: 10) --help # Full usage ``` **Examples:** ```bash # 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`
Related Skills
Testing Anti-Patterns
Never test mock behavior. Never add test-only methods to production classes. Understand dependencies before mocking.
Test-Driven Development (TDD)
Write the test first, watch it fail, write minimal code to pass
Condition-Based Waiting
Replace arbitrary timeouts with condition polling for reliable async tests
Testing Skills With Subagents
RED-GREEN-REFACTOR for process documentation - baseline without skill, write addressing failures, iterate closing loopholes
Installing Skills System
Fork, clone to ~/.clank, run installer, edit CLAUDE.md
Gardening Skills Wiki
Maintain skills wiki health - check links, naming, cross-references, and coverage
Creating Skills
TDD for process documentation - test with subagents before writing, iterate until bulletproof
Getting Started with Skills
Skills wiki intro - mandatory workflows, search tool, brainstorming triggers
Verification Before Completion
Run verification commands and confirm output before claiming success
Systematic Debugging
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
Root Cause Tracing
Systematically trace bugs backward through call stack to find original trigger
Defense-in-Depth Validation
Validate at every layer data passes through to make bugs impossible