What problem does it solve?
After development cycles, valuable durable knowledge like module boundary changes, technical decisions, and recurring pitfalls gets lost in ephemeral task notes, scattered logs, and informal discussions, leading to repeated mistakes and lost institutional context for engineering teams.
Core Features & Use Cases
- Durable Knowledge Identification: Automatically surfaces high-value insights from specs, designs, code reviews, commits, and delivery cycle artifacts that are worth preserving long-term.
- Structured Memory Organization: Selects the correct canonical document type (module cards, contracts, decisions, runbooks, lessons) to categorize and standardize preserved knowledge.
- Noise Reduction: Updates existing repository memory documents first to avoid duplicates, and explicitly tracks knowledge gaps and non-durable candidates to keep memory clean.
- Use Case: After a major payment module refactor that changed core interface contracts, use this skill to update the relevant contract docs and module cards, and record the new compatibility rules so all team members have access to accurate, up-to-date context.
Quick Start
Use the curating-repository-memory skill to update the canonical repository memory with durable insights from the recent authentication service refactor and formal commit a1b2c3d.
