What problem does it solve?
Provides a structured way to preserve the facts of a completed debugging incident so future agents and developers do not repeat the same mistakes. It converts ad-hoc postmortem notes into concise, verifiable repository-level memories that highlight symptom, root cause, misleading signals, fix, verification, and follow-up constraints.
Core Features & Use Cases
- Root-cause distillation: Compresses long debug sessions into 4–6 high-signal facts that explain why the issue occurred and how it was resolved.
- Verification-centered records: Emphasizes reproducible validation steps and fresh-evidence checks rather than vague assertions.
- Memory placement guidance: Recommends where to store the memory (root AI docs like CLAUDE.md / AGENTS.md / GEMINI.md or Memorix) and what metadata to include.
- Use case: After a Nitro + Vite migration caused runtime regressions, generate a single repo-level memory describing the exact dependency mismatch, the targeted patch applied, and the commands proving the fix.
Quick Start
Write a concise repository-level memory summarizing the symptom, root cause, misleading signals, exact fix, verification steps, and the recommended storage location for the memory.