memory-merger
installsforks
How to install memory-merger?
github/awesome-copilot/memory-merger
$npx -y skills add github/awesome-copilot --skill memory-mergerMerges 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.
SKILL.md
| 1 | # Memory Merger |
| 2 | |
| 3 | You consolidate mature learnings from a domain's memory file into its instruction file, ensuring knowledge preservation with minimal redundancy. |
| 4 | |
| 5 | **Use the todo list** to track your progress through the process steps and keep the user informed. |
| 6 | |
| 7 | ## Scopes |
| 8 | |
| 9 | Memory instructions can be stored in two scopes: |
| 10 | |
| 11 | - **Global** (`global` or `user`) - Stored in `<global-prompts>` (`vscode-userdata:/User/prompts/`) and apply to all VS Code projects |
| 12 | - **Workspace** (`workspace` or `ws`) - Stored in `<workspace-instructions>` (`<workspace-root>/.github/instructions/`) and apply only to the current project |
| 13 | |
| 14 | Default scope is **global**. |
| 15 | |
| 16 | Throughout this prompt, `<global-prompts>` and `<workspace-instructions>` refer to these directories. |
| 17 | |
| 18 | ## Syntax |
| 19 | |
| 20 | ``` |
| 21 | /memory-merger >domain-name [scope] |
| 22 | ``` |
| 23 | |
| 24 | - `>domain-name` - Required. The domain to merge (e.g., `>clojure`, `>git-workflow`, `>prompt-engineering`) |
| 25 | - `[scope]` - Optional. One of: `global`, `user` (both mean global), `workspace`, or `ws`. Defaults to `global` |
| 26 | |
| 27 | **Examples:** |
| 28 | - `/memory-merger >prompt-engineering` - merges global prompt engineering memories |
| 29 | - `/memory-merger >clojure workspace` - merges workspace clojure memories |
| 30 | - `/memory-merger >git-workflow ws` - merges workspace git-workflow memories |
| 31 | |
| 32 | ## Process |
| 33 | |
| 34 | ### 1. Parse Input and Read Files |
| 35 | |
| 36 | - **Extract** domain and scope from user input |
| 37 | - **Determine** file paths: |
| 38 | - Global: `<global-prompts>/{domain}-memory.instructions.md` → `<global-prompts>/{domain}.instructions.md` |
| 39 | - Workspace: `<workspace-instructions>/{domain}-memory.instructions.md` → `<workspace-instructions>/{domain}.instructions.md` |
| 40 | - 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. |
| 41 | - **Read** both files (memory file must exist; instruction file may not) |
| 42 | |
| 43 | ### 2. Analyze and Propose |
| 44 | |
| 45 | Review all memory sections and present them for merger consideration: |
| 46 | |
| 47 | ``` |
| 48 | ## Proposed Memories for Merger |
| 49 | |
| 50 | ### Memory: [Headline] |
| 51 | **Content:** [Key points] |
| 52 | **Location:** [Where it fits in instructions] |
| 53 | |
| 54 | [More memories]... |
| 55 | ``` |
| 56 | |
| 57 | Say: "Please review these memories. Approve all with 'go' or specify which to skip." |
| 58 | |
| 59 | **STOP and wait for user input.** |
| 60 | |
| 61 | ### 3. Define Quality Bar |
| 62 | |
| 63 | Establish 10/10 criteria for what constitutes awesome merged resulting instructions: |
| 64 | 1. **Zero knowledge loss** - Every detail, example, and nuance preserved |
| 65 | 2. **Minimal redundancy** - Overlapping guidance consolidated |
| 66 | 3. **Maximum scannability** - Clear hierarchy, parallel structure, strategic bold, logical grouping |
| 67 | |
| 68 | ### 4. Merge and Iterate |
| 69 | |
| 70 | Develop the final merged instructions **without updating files yet**: |
| 71 | |
| 72 | 1. Draft the merged instructions incorporating approved memories |
| 73 | 2. Evaluate against quality bar |
| 74 | 3. Refine structure, wording, organization |
| 75 | 4. Repeat until the merged instructions meet 10/10 criteria |
| 76 | |
| 77 | ### 5. Update Files |
| 78 | |
| 79 | Once the final merged instructions meet 10/10 criteria: |
| 80 | |
| 81 | - **Create or update** the instruction file with the final merged content |
| 82 | - Include proper frontmatter if creating new file |
| 83 | - **Merge `applyTo` patterns** from both memory and instruction files if both exist, ensuring comprehensive coverage without duplication |
| 84 | - **Remove** merged sections from the memory file |
| 85 | |
| 86 | ## Example |
| 87 | |
| 88 | ``` |
| 89 | User: "/memory-merger >clojure" |
| 90 | |
| 91 | Agent: |
| 92 | 1. Reads clojure-memory.instructions.md and clojure.instructions.md |
| 93 | 2. Proposes 3 memories for merger |
| 94 | 3. [STOPS] |
| 95 | |
| 96 | User: "go" |
| 97 | |
| 98 | Agent: |
| 99 | 4. Defines quality bar for 10/10 |
| 100 | 5. Merges new instructions candidate, iterates to 10/10 |
| 101 | 6. Updates clojure.instructions.md |
| 102 | 7. Cleans clojure-memory.instructions.md |
| 103 | ``` |
People who liked this also viewed
6 picksType
- lark-drive飞书云空间（云盘/云存储）：管理 Drive 文件和文件夹，包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、评论/权限/订阅、标题、版本、飞书文档密级标签（secure labels）和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题，或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sSkillsJul 2026
- lark-sharedUse for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handlingSkillsJul 2026
- lark-whiteboard飞书画板：查询和编辑飞书云文档中的画板。支持导出画板为预览图片、导出原始节点结构、使用多种格式更新画板内容。 当用户需要查看画板内容、导出画板图片、编辑画板时使用此 skill。不负责：飞书云文档内容编辑（lark-doc）、文档内嵌电子表格/Base（lark-sheets / lark-base）。SkillsJul 2026
- lark-task飞书任务：管理任务、清单和任务智能体。创建待办任务、查看和更新任务状态、拆分子任务、组织任务清单、分配协作成员、上传任务附件、注册或注销任务智能体、更新任务智能体的主页数据、写入智能体任务记录。当用户需要创建待办事项、查看任务列表、跟踪任务进度、管理项目清单或给他人分配任务、为任务上传附件文件、注册注销任务智能体、更新智能体主页数据、写入任务记录时使用。SkillsJul 2026
- lark-attendance飞书考勤打卡：查询自己的考勤打卡记录SkillsJul 2026
- lark-apps妙搭（Spark/Miaoda）应用开发与托管：应用创建、本地全栈开发、云端生成迭代、创意设计（UI mockup / 可交互原型 / 线框图 / 落地页 / 仪表盘 / 幻灯片 deck / 视觉探索）、AI相关能力和飞书平台能力或者其他外部能力集成、日志/Trace/监控指标/PV/UV 查询、环境变量管理、应用角色与成员管理、自动化触发器（定时/记录变更/Webhook/飞书审批）。当用户要SkillsJul 2026
