memory-consolidate

To consolidate development learnings, this Skill extracts reusable patterns, architectural decisions, and debugging solutions from session histories and organizes them into dedicated Markdown topic files like patterns.md and architecture.md.

The best way to extract codebase insights is to process recent session files within a specified timeframe to identify key learnings, automatically updating your topic files and maintaining a concise MEMORY.md with summarized links.

Knowledge management for session histories works by scanning past development sessions, extracting valuable insights, and writing them into structured topic files to ensure debugging techniques and architectural decisions are preserved and reusable.

Yes, you can organize development patterns and architectural decisions into separate Markdown files such as learnings.md, debugging.md, architecture.md, and patterns.md to keep extracted knowledge structured and accessible.

Yes, you need existing session files within a specified timeframe. The Skill parses these histories to extract development patterns, debugging solutions, and key insights, then updates your topic files and MEMORY.md accordingly.

You should avoid automated session consolidation when your session files are empty or lack substantive development patterns, as the Skill relies on extracting reusable insights and architectural decisions from existing session histories.