How does Memory Search store data?

It uses a local DuckDB database located at ~/.claude/context_memory.duckdb to store and index categorized observations from your sessions.

What types of information are tracked by this skill?

It tracks various observation types including architectural decisions (D), bugfixes (B), features (F), refactors (R), discoveries (i), and general changes (C).

Can it search across different git branches?

Yes, the skill can retrieve context specific to a designated branch or provide a global history of all project activity.

Does it require an internet connection to work?

No, because the memory is stored in a local database on your machine, the search functionality works offline within your local environment.

Memory Search

Name: Memory Search
Author: PedroGiudice

byPedroGiudice

•

Productivity & Workflow

Recalls past project context and implementation decisions from previous Claude Code sessions using a persistent database.

About

Memory Search provides Claude with long-term memory capabilities by storing and querying observations from previous work sessions. This skill allows users to ask questions about past implementations, architectural decisions, and bug fixes that occurred outside the current context window. By leveraging a local DuckDB database, it tracks features, refactors, and discoveries across different branches, ensuring that historical project knowledge is always accessible and that development consistency is maintained over time.

Key Features

Branch-specific context filtering and historical summaries
Statistical insights into project activity and implementation progress
Cross-session context retrieval for multi-day development cycles
Categorized observation tracking for decisions, bugfixes, and features
Full-text search capabilities across past command history and findings
1 GitHub stars

Use Cases

Recalling the specific reasoning behind an architectural decision made in a previous session
Maintaining implementation consistency when switching between different git branches
Onboarding onto a complex project by reviewing a summary of recent features and bugfixes

About

Key Features

Branch-specific context filtering and historical summaries
Statistical insights into project activity and implementation progress
Cross-session context retrieval for multi-day development cycles
Categorized observation tracking for decisions, bugfixes, and features
Full-text search capabilities across past command history and findings
1 GitHub stars

Use Cases

Recalling the specific reasoning behind an architectural decision made in a previous session
Maintaining implementation consistency when switching between different git branches
Onboarding onto a complex project by reviewing a summary of recent features and bugfixes