record-bug-fix-memory

Record bug-fix memories with root cause and verification steps into repository files.

Updated Sep 11, 2025
One-click install
npx skills add https://github.com/ruan-cat/11comm-app --skill record-bug-fix-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: record-bug-fix-memory
Source: https://github.com/ruan-cat/11comm-app/tree/main/.claude/skills/fix-bug/record-bug-fix-memory
Command: npx skills add https://github.com/ruan-cat/11comm-app --skill record-bug-fix-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about record-bug-fix-memory

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

FAQPage Schema
How do I record a bug fix memory for a postmortem?

To record a bug fix memory, distill the incident into 4-6 high-signal facts covering symptom, root cause, exact fix, and verification steps, then store the entry in a repository-level destination like CLAUDE.md or Memorix.

What should be included in an incident report to prevent repeated debugging?

An incident report memory should include the symptom, root cause, misleading signals encountered during debugging, the exact fix applied, reproducible verification steps, and follow-up constraints to prevent repeated mistakes.

How do I write a postmortem for a runtime regression after a framework migration?

Write a postmortem by compressing the debug session into concise facts detailing the dependency mismatch, the targeted patch applied, and the commands proving the fix, ensuring the memory is verifiable.

Where should I store agent handoff memories for bug fixes?

Agent handoff memories should be stored in root AI docs like CLAUDE.md, AGENTS.md, or GEMINI.md, or within Memorix, ensuring future agents access the root cause and validation evidence directly.

Do I need a reproduced fix before generating a knowledge-base entry?

Yes, a reproduced fix is required. The memory generation process mandates clear verification steps and fresh-evidence checks rather than vague assertions to ensure the bug fix is verifiable.

Can I use this for repository-level postmortems without Memorix?

Yes, you can use this for repository-level postmortems without Memorix by targeting alternative memory destinations such as root AI documentation files like CLAUDE.md, AGENTS.md, or GEMINI.md.