memory-merger

Merging memory files into instruction files requires parsing user input for domain and scope, reading both files, analyzing content quality, and updating the primary instruction file while cleaning the memory file. This reduces redundancy and preserves validated learnings.

Knowledge consolidation can be managed across global (user-wide) and workspace-specific (project-wide) scopes. You specify the desired scope in your input, and the merger processes the corresponding memory and instruction files to ensure information is preserved without duplication.

Yes, you can merge validated learnings from a specific domain like git-workflow. The process reads the domain's memory file, analyzes the mature lessons for quality, and integrates them seamlessly into your project's primary instruction set for consistent application.

Yes, knowledge consolidation works for both global and workspace-specific memory scopes. The skill processes memory and instruction files based on the scope you define in your input, managing knowledge preservation across user-wide or project-wide contexts.

Merging memory into instruction files reduces redundancy by analyzing content quality and moving mature lessons from temporary memory files into permanent instruction files. The memory file is then cleaned, preventing duplicate knowledge storage.

You should use automated knowledge consolidation when you have refined mature lessons in a memory file and want to integrate them seamlessly into a primary instruction set. This prevents knowledge loss and minimizes redundancy across your domain memory.