Memory Merger
- 12.7k installs
- 37.1k repo stars
- Updated July 28, 2026
- github/awesome-copilot
Memory Merger is a skill that consolidates learnings from domain memory files into instruction files.
About
A skill for merging domain learnings from memory files into instruction files. Consolidates knowledge across global or workspace scopes while maintaining zero knowledge loss and minimal redundancy. Useful for organizing accumulated insights and best practices.
- Consolidate mature learnings from domain memory files
- Merge into instruction files with minimal redundancy
- Support global and workspace scopes
Memory Merger by the numbers
- 12,694 all-time installs (skills.sh)
- +37 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #87 of 3,301 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: HIGH risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
memory-merger capabilities & compatibility
- Capabilities
- knowledge consolidation · instruction management · file organization
What memory-merger says it does
You consolidate mature learnings from a domain's memory file into its instruction file, ensuring knowledge preservation with minimal redundancy.
npx skills add https://github.com/github/awesome-copilot --skill memory-mergerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 12.7k |
|---|---|
| repo stars | ★ 37.1k |
| Security audit | 2 / 3 scanners passed |
| Last updated | July 28, 2026 |
| Repository | github/awesome-copilot ↗ |
How do you merge copilot memory into instruction files?
Knowledge organization and documentation for developer workflows.
Who is it for?
Developers managing evolving knowledge bases and instruction sets.
Skip if: Greenfield projects with no domain memory file or teams that store agent rules only in a single static prompts document.
When should I use this skill?
Domain memory files contain repeated or mature lessons that should live in the canonical instruction file for a global, user, or workspace scope.
What you get
Updated instruction file, deduplicated domain knowledge, and preserved mature lessons from memory.
- Updated instruction file
- Deduplicated domain knowledge archive
Files
Memory Merger
You consolidate mature learnings from a domain's memory file into its instruction file, ensuring knowledge preservation with minimal redundancy.
Use the todo list to track your progress through the process steps and keep the user informed.
Scopes
Memory instructions can be stored in two scopes:
- Global (
globaloruser) - Stored in<global-prompts>(vscode-userdata:/User/prompts/) and apply to all VS Code projects - Workspace (
workspaceorws) - Stored in<workspace-instructions>(<workspace-root>/.github/instructions/) and apply only to the current project
Default scope is global.
Throughout this prompt, <global-prompts> and <workspace-instructions> refer to these directories.
Syntax
/memory-merger >domain-name [scope]>domain-name- Required. The domain to merge (e.g.,>clojure,>git-workflow,>prompt-engineering)[scope]- Optional. One of:global,user(both mean global),workspace, orws. Defaults toglobal
Examples:
/memory-merger >prompt-engineering- merges global prompt engineering memories/memory-merger >clojure workspace- merges workspace clojure memories/memory-merger >git-workflow ws- merges workspace git-workflow memories
Process
1. Parse Input and Read Files
- Extract domain and scope from user input
- Determine file paths:
- Global:
<global-prompts>/{domain}-memory.instructions.md→<global-prompts>/{domain}.instructions.md - Workspace:
<workspace-instructions>/{domain}-memory.instructions.md→<workspace-instructions>/{domain}.instructions.md - The user can have mistyped the domain, if you don't find the memory file, glob the directory and determine if there may be a match there. Ask the user for input if in doubt.
- Read both files (memory file must exist; instruction file may not)
2. Analyze and Propose
Review all memory sections and present them for merger consideration:
## Proposed Memories for Merger
### Memory: [Headline]
**Content:** [Key points]
**Location:** [Where it fits in instructions]
[More memories]...Say: "Please review these memories. Approve all with 'go' or specify which to skip."
STOP and wait for user input.
3. Define Quality Bar
Establish 10/10 criteria for what constitutes awesome merged resulting instructions: 1. Zero knowledge loss - Every detail, example, and nuance preserved 2. Minimal redundancy - Overlapping guidance consolidated 3. Maximum scannability - Clear hierarchy, parallel structure, strategic bold, logical grouping
4. Merge and Iterate
Develop the final merged instructions without updating files yet:
1. Draft the merged instructions incorporating approved memories 2. Evaluate against quality bar 3. Refine structure, wording, organization 4. Repeat until the merged instructions meet 10/10 criteria
5. Update Files
Once the final merged instructions meet 10/10 criteria:
- Create or update the instruction file with the final merged content
- Include proper frontmatter if creating new file
- Merge `applyTo` patterns from both memory and instruction files if both exist, ensuring comprehensive coverage without duplication
- Remove merged sections from the memory file
Example
User: "/memory-merger >clojure"
Agent:
1. Reads clojure-memory.instructions.md and clojure.instructions.md
2. Proposes 3 memories for merger
3. [STOPS]
User: "go"
Agent:
4. Defines quality bar for 10/10
5. Merges new instructions candidate, iterates to 10/10
6. Updates clojure.instructions.md
7. Cleans clojure-memory.instructions.mdRelated skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.645k185kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.547k185k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.466kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).466kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.466kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.465kHow it compares
Choose memory-merger to promote durable lessons into instructions; use fresh memory files when experimentation should stay separate from canonical rules.
FAQ
What is the memory-merger command syntax?
memory-merger runs as `/memory-merger >domain [scope]` where scope is global (default), user, workspace, or ws, targeting a named domain’s memory and instruction pair.
Where do global memory-merger changes persist?
memory-merger stores global and user scoped instructions in VS Code global prompts at the vscode-userdata user prompts location so guidance applies across projects.
What does memory-merger do with duplicate lessons?
memory-merger promotes mature entries from the domain memory file into the instruction file while collapsing redundant copies so one canonical instruction set remains.
Is Memory Merger safe to install?
skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.