error-memory

Persist failed approaches, working solutions, and recurring bugs across debugging sessions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nhouseholder/nicks-claude-code-superpowers --skill error-memory-nhouseholder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: error-memory
Source: https://github.com/nhouseholder/nicks-claude-code-superpowers/tree/main/skills/error-memory
Command: npx skills add https://github.com/nhouseholder/nicks-claude-code-superpowers --skill error-memory-nhouseholder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Captures and persists failed approaches, working solutions, and recurring bugs from debugging sessions to prevent token waste and repetitive work.

Core Features & Use Cases

  • Tracks anti-patterns and recurring bugs across sessions
  • Escalates root-cause analysis for repeated issues
  • Persists memory for future debugging workflows

Quick Start

Start capturing after a debugging session completes and persist key lessons for future runs.

Frequently Asked Questions about error-memory

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

FAQPage Schema
How do I track recurring bugs across multiple debugging sessions?▼

Tracking recurring bugs across debugging sessions requires persisting failed approaches and working solutions in a cross-session memory agent. This Skill captures anti-patterns and integrates user corrections to maintain persistent records for future workflows.

What is the best way to prevent token waste from repeating the same debugging fixes?▼

Preventing token waste during debugging is achieved by persisting failed approaches and working solutions after each session. This Skill escalates root-cause analysis for repeated issues, eliminating repetitive work across codebases.

How do I persist failed approaches after a debugging session completes?▼

Persisting failed approaches starts after a debugging session completes. You capture key lessons, track anti-patterns, and trigger persistent records through an error-memory agent that manages cross-session memory and integrates user corrections.

Can I use this to escalate root-cause analysis for bugs that keep reappearing?▼

Escalating root-cause analysis for reappearing bugs is a core function. The Skill identifies patterns where errors occur repeatedly and escalates the analysis to address the underlying root cause rather than just the symptoms.

Do I need a specific environment setup to track anti-patterns across codebases?▼

Tracking anti-patterns across codebases requires an error-memory agent capable of cross-session memory management. The Skill operates within development workflows and QA environments where errors occur repeatedly and patterns emerge.