Consolidates mature learnings from domain memory files into instruction files with quality-assured merging.
Works with
Operates on two scopes: global (VS Code user prompts) and workspace (project-specific instructions), with configurable domain targeting
Requires explicit user approval before merging, presenting proposed memories for review with proposed locations in the instruction hierarchy
Enforces a 10/10 quality bar during merge: zero knowledge loss, minimal redundancy, and maximum scannab
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionmemory-mergerExecute the skills CLI command in your project's root directory to begin installation:
Fetches memory-merger from github/awesome-copilot and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate memory-merger. Access via /memory-merger in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
1
total installs
1
this week
28.7K
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
28.7K
stars
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.
Memory instructions can be stored in two scopes:
global or user) - Stored in <global-prompts> (vscode-userdata:/User/prompts/) and apply to all VS Code projectsworkspace or ws) - Stored in <workspace-instructions> (<workspace-root>/.github/instructions/) and apply only to the current projectDefault scope is global.
Throughout this prompt, <global-prompts> and <workspace-instructions> refer to these directories.
/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, or ws. Defaults to globalExamples:
/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<global-prompts>/{domain}-memory.instructions.md → <global-prompts>/{domain}.instructions.md<workspace-instructions>/{domain}-memory.instructions.md → <workspace-instructions>/{domain}.instructions.mdReview 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.
Establish 10/10 criteria for what constitutes awesome merged resulting instructions:
Develop the final merged instructions without updating files yet:
Once the final merged instructions meet 10/10 criteria:
applyTo patterns from both memory and instruction files if both exist, ensuring comprehensive coverage without duplicationUser: "/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.md
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
github/awesome-copilot
github/awesome-copilot
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
memory-merger is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: memory-merger is focused, and the summary matches what you get after install.
memory-merger fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in memory-merger — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
memory-merger has been reliable in day-to-day use. Documentation quality is above average for community skills.
memory-merger reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for memory-merger matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in memory-merger — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added memory-merger from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
memory-merger has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 67