debugging-memory

Recall past incidents from local memory before debugging new bugs.

2|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/tyroneross/claude-code-debugger --skill debugging-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging-memory
Source: https://github.com/tyroneross/claude-code-debugger/tree/main/skills/debugging-memory
Command: npx skills add https://github.com/tyroneross/claude-code-debugger --skill debugging-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically leverage debugging memory to recall past incidents before solving a new bug.

Core Features & Use Cases

  • Memory-backed incident search to surface previous fixes
  • Pattern extraction and reusable solutions for common bugs
  • Subagent coordination with memory context to accelerate investigations

Quick Start

Run a memory-aware debugging session: npx @tyroneross/claude-code-debugger debug "<symptom description>"

Frequently Asked Questions about debugging-memory

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

FAQPage Schema
How do I use past debugging incidents to fix a new bug?

You can recall past debugging incidents by running a memory-aware debugging session that automatically searches your local memory store for previous fixes before investigating the new bug. It surfaces pattern matches to provide prioritized fixes and investigation starting points.

Can I coordinate subagents with memory context during multi-agent debugging?

Yes, subagent coordination with memory context is supported to accelerate incident investigations. It allows multiple agents to leverage the shared memory store of past debugging patterns and incident solutions during the workflow.

What do I need to set up before running a memory-aware debugging session?

You need access to a local memory store, such as a .claude/memory/incidents directory, to retain past bug fixes and incident patterns. The debugging tool queries this local store to extract and retrieve reusable solutions for pattern matching.

Does debugging memory support pattern matching for common software bugs?

Yes, debugging memory supports pattern extraction and retrieval to find reusable solutions for common software bugs. It automatically matches the current bug symptoms against stored incident patterns to prioritize the most relevant fixes.

How do I search local incident memory for a specific error symptom?

You can search local incident memory by running the debug command with a symptom description string. The tool queries the local memory store, matches the description against past patterns, and outputs prioritized investigation starting points based on similar previous incidents.