memory-manager

Solid

Standardized workflow for discovering, reading, writing, and compacting the project's memory file (memory.instructions.md) to persist context across AI chat sessions, with a permanent Knowledge Base for cross-session decisions and lessons learned.

AI & Automation 73 stars 13 forks Updated today MIT

Install

View on GitHub

Quality Score: 87/100

Stars 20%
62
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

<!-- markdownlint-disable --> # Memory Manager Skill ## Overview This skill provides a standardized protocol for managing the project's persistent memory file (`memory.instructions.md`). It ensures that AI agents can reliably save and restore context across chat sessions, regardless of which instruction directory the project uses. This skill is **agent-agnostic** โ€” any agent in the ecosystem can invoke it. The memory file is divided into **two distinct zones**: 1. **๐Ÿง  Knowledge Base** โ€” A permanent section at the top that accumulates cross-session knowledge: architectural decisions, proven patterns, dead-ends with root causes, and key metrics. This section survives compaction and is never deleted. 2. **๐Ÿ“ Session Checkpoints** โ€” Append-only entries at the bottom that track per-session progress. These are rotated during compaction, with valuable knowledge promoted to the Knowledge Base before deletion. For performance, the active memory path can be recorded in the project's `AGENTS.md` file as a fast-path shortcut. See **AGENTS.md Integration** below for details. ## When to Use - **Write Mode:** At the end of a significant milestone or phase completion, when the user agrees to save progress. - **Read Mode:** At the start of a new chat session to bootstrap context from prior sessions. - **Compaction Mode:** When the user requests cleanup of old checkpoints, promoting valuable knowledge to the Knowledge Base before deleting stale entries. --- ## Workflow 1: File Disco...

Details

Author
GulajavaMinistudio
Repository
GulajavaMinistudio/awesome-copilot-id
Created
9 months ago
Last Updated
today
Language
JavaScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content โ€” not just same category

AI & Automation Listed

session-memory-manager

Manages Claude Code's persistent memory system โ€” auto-memory files, cross-session context, project memory directories, and task handoff protocols. Use when organizing session memory, creating handoff documents, managing MEMORY.md files, or establishing continuity between Claude Code sessions.

4 Updated 1 months ago
AreteDriver
AI & Automation Listed

memory-system

Maintain a tiered, file-based memory system so project context and decisions survive across sessions instead of being rediscovered or contradicted each time.

1 Updated 4 days ago
niels-emmer
AI & Automation Listed

memo-session-skill

Persistent AI agent memory for coding sessions โ€” cross-session knowledge that survives context window resets. Consolidates session noise into durable facts and routes them via memory routing into MEMORY.md, memory/ HOT/WARM/COLD layers, project wiki, AGENTS.md, skills, and optional portfolio memory โ€” git-tracked, with conflict gate and temperature limits. Stateful handoff when volatile chat context is lost; complements vector RAG or managed memory platforms, does not replace them. Use when the user says "wrap up the session", "save what we learned", "handoff", "open loops", "update memory", "agent memory", "persistent memory", "cross-session persistence", "how to give my agent memory", or when another skill requests a memory checkpoint. Also for portfolio/global memory, bootstrap project memory, session changelog, `/inbox`, process inbox, or ingest files from memory/inbox. When memo-session-mcp is connected, use search_all for portfolio/project lookup and reindex_changed after writes. Prefer after non-trivial

2 Updated 5 days ago
shenwell