Is testing required for this debugging workflow?

Yes, Phase 4 of the process requires creating a failing test case before implementing a fix to ensure the root cause is truly addressed and remains fixed.

What happens if a bug is still not fixed after three attempts?

The framework triggers an architectural review. If three fixes fail, it suggests the problem is likely in the fundamental design rather than a simple implementation error.

Why does this skill forbid quick fixes?

Quick fixes often mask symptoms rather than solving the underlying root cause, which leads to recurring bugs, technical debt, and new issues in related components.

How does this skill handle multi-component system failures?

It implements diagnostic instrumentation at every component boundary to log data entry and exit, allowing you to isolate exactly where a failure occurs before changing code.

Systematic Debugging Framework

Name: Systematic Debugging Framework
Author: ed3dai

byed3dai

•

Security & Testing

Implements a rigorous four-phase methodology to identify root causes and ensure stable, test-backed resolutions for complex software issues.

The Systematic Debugging skill provides Claude with a strict, research-first framework designed to eliminate guesswork and trial-and-error bug fixing. By enforcing a mandatory sequence of root cause investigation, pattern analysis, and minimal hypothesis testing before any code is modified, it ensures that developers solve underlying issues rather than masking symptoms. This approach is particularly effective for multi-component systems, intermittent failures, and scenarios where previous quick fixes have failed, ultimately reducing development thrashing and technical debt.

Key Features

01Evidence-based pattern analysis comparing broken code against working reference implementations

02Architectural safety triggers that halt development when multiple fix attempts reveal systemic issues

03Diagnostic instrumentation for tracing errors across complex multi-layer system boundaries

04Integration with Test-Driven Development (TDD) to verify fixes with failing test cases

0545 GitHub stars

06Mandatory four-phase debugging framework: Investigation, Analysis, Hypothesis, and Implementation

Use Cases

01Resolving persistent bugs that have resisted multiple 'quick fix' attempts or temporary patches

02Performing deep-dive root cause analysis on production incidents and performance regressions

03Debugging intermittent or 'flaky' failures in complex CI/CD pipelines or microservices

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add ed3dai/ed3d-plugins systematic-debugging

For use in Claude.ai and ChatGPT

Download Skill