memory-merger

Merges mature lessons from domain memory files into VS Code instruction files.

1|1|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill memory-merger-ultraviollettnympho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-merger
Source: https://github.com/ultraviollettnympho/transit-ticket/tree/main/.github/skills/memory-merger
Command: npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill memory-merger-ultraviollettnympho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Over time, domain memory files accumulate lessons that belong in permanent instruction files, but manually consolidating them risks knowledge loss and redundancy. This Skill guides an AI agent through a structured, review-gated merger process that preserves every detail while keeping instructions scannable. ## Core Features & Use Cases - Scoped Merging: Supports global (user-level) and workspace instruction scopes with flexible syntax like /memory-merger >domain [scope]. - Review-Gated Workflow: Proposes each memory for approval and waits for user confirmation before modifying any files. - Quality-Bar Iteration: Defines a 10/10 quality bar (zero knowledge loss, minimal redundancy, maximum scannability) and iterates on the merged draft before writing. - Use Case: After weeks of accumulating Clojure tips in a memory file, run /memory-merger >clojure workspace to fold the mature lessons into the project's clojure.instructions.md and clean up the memory file. ## Quick Start Ask the agent to run /memory-merger >your-domain with an optional scope such as global or workspace to consolidate that domain's memory file into its instruction file.

Frequently Asked Questions about memory-merger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I merge a memory file into an instruction file in VS Code?

Run /memory-merger >domain-name with an optional scope. The agent reads the domain's memory and instruction files, proposes each memory for your approval, then merges approved content and cleans the memory file.

What is the difference between global and workspace scope for instructions?

Global scope stores instructions in the VS Code user prompts directory and applies to all projects. Workspace scope stores them in .github/instructions/ inside the project and applies only to that repository. Global is the default.

Can I approve only some memories during the merge?

Yes. After the agent proposes memories, reply 'go' to approve all of them or specify which ones to skip. The agent stops and waits for your input before changing any files.

What happens if the domain memory file is not found?

The agent globs the prompts or instructions directory to find possible matches for a mistyped domain name and asks you for confirmation if it is unsure which file you meant.

Does the merge lose any details from the memory file?

No. The process defines a quality bar requiring zero knowledge loss, minimal redundancy, and maximum scannability, and the agent iterates on the merged draft until it meets that bar before updating files.