serena-memory

Store, recall, list, and delete persistent project memories for Serena MCP.

Updated Jun 17, 2025

Search Tags:#architecture #context #memory management #memory #persistence #notes

Ready to run

npx skills add https://github.com/Karlito8888/new-ggv-gps --skill serena-memory

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: serena-memory
Source: https://github.com/Karlito8888/new-ggv-gps/tree/main/.claude/skills/serena-memory
Command: npx skills add https://github.com/Karlito8888/new-ggv-gps --skill serena-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides durable memory storage to preserve architectural decisions, patterns, and context between sessions.

Core Features & Use Cases

Store memory: Save decisions, patterns, or contextual notes.
Recall memory: Retrieve stored memories by key or category.
List memories: Browse all stored memories.
Delete memory: Clean obsolete entries.

Quick Start

Store a memory with key "routing_strategy" and later recall it to guide routing decisions.

Frequently Asked Questions about serena-memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I persist project context across development sessions?▼

Persistent project memory stores architectural decisions, coding patterns, and contextual history between sessions. This Skill captures and retrieves that information using key-based storage and category tagging, so you can recall decisions made in prior work cycles without re-documenting.

Can I store and retrieve architectural decisions for long-term reference?▼

Yes. Store architectural decisions, resolved bugs, and patterns with descriptive keys and categories, then retrieve them by key or category across sessions. This enables teams to maintain continuous context through onboarding, debugging, and development cycles.

What's the best way to organize project memories by category?▼

Assign category tags when storing memories alongside descriptive keys. List all stored memories to browse by category, and delete obsolete entries to keep your context clean. This structure lets you recall related decisions and patterns quickly during development.

How do I manage memory entries when my project evolves?▼

Store new memories with updated keys and categories as your project changes. List existing memories to track what's documented, and delete outdated entries. This keeps your persistent context aligned with current architecture and patterns.

Can memory persistence work across different development phases?▼

Yes. Memory storage satisfies functional requirements across onboarding, debugging, and development cycles. Store decisions once, then retrieve them in any phase to maintain continuous architectural and pattern context regardless of when team members rejoin the project.