Agent skill · software engineering · github
memory-merger
Merges mature lessons from a domain memory file into its instruction file. Syntax: `/memory-merger >domain [scope]` where scope is `global` (default), `user`, `workspace`, or `ws`.
Why this skill is useful
Adds a specific command syntax and process for merging domain memories into instruction files that the AI wouldn't reliably generate on its own.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
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 (global or user) - Stored in <global-prompts> (vscode-userdata:/User/prompts/) and apply to all VS Code projects Workspace (workspace or ws) - 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 domain-name - Required. The domain to merge (e.g., >clojure, >git-workflow, >prompt-engineering) [scope] - Optional. One of: global, user (both mean global), workspace, or ws. Defaults to global 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: Say: "Please review these memories. Approve all with 'go' or specify which to skip." STOP and wait for user input. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/memory-merger