Do I need to write tests for every bug using this skill?

Yes. Phase 4 requires creating a failing test case before implementing a fix. This ensures the bug is reproducible and provides automated verification that the final fix actually works.

What happens if three consecutive fix attempts fail?

The skill triggers a mandatory 'Stop and Question Architecture' phase. This prevents endless thrashing by encouraging the agent to discuss fundamental design flaws with the human partner instead of applying a fourth patch.

What is the 'Iron Law' of systematic debugging?

The Iron Law states that no fixes should be proposed or attempted until a thorough root cause investigation (Phase 1) is completed. This prevents 'masking' symptoms while leaving underlying issues unresolved.

How does this skill handle multi-component systems?

It adds diagnostic instrumentation at component boundaries to log data entry and exit, verifying environment propagation at each layer to isolate exactly where the system breaks.

Systematic Debugging

Name: Systematic Debugging
Author: noeljackson

bynoeljackson

0•

安全与测试

Implements a rigorous four-phase debugging protocol to identify root causes and prevent regression-prone quick fixes.

The Systematic Debugging skill enforces a disciplined approach to software troubleshooting by prioritizing root cause investigation over symptomatic patching. It guides Claude through a structured workflow—from evidence gathering and pattern analysis to minimal hypothesis testing and final verification—ensuring that every fix is backed by data and a reproducible test case. This approach is particularly effective for complex, multi-layered systems where random 'guess-and-check' attempts often lead to architectural debt or cascading failures, ensuring higher first-time fix rates and long-term code stability.

主要功能

01Provides specialized diagnostic instrumentation for multi-component system boundaries

020 GitHub stars

03Enforces the 'Iron Law' of no fixes without completed root cause investigation

04Guides backward data flow tracing to find the original trigger of deep call stack errors

05Mandates the creation of a failing test case before any implementation phase begins

06Implements a 3-fix limit that triggers mandatory architectural review if issues persist

使用场景

01Resolving deep logic errors where the symptom appears far from the actual bug source

02Debugging intermittent failures in complex CI/CD pipelines or distributed systems

03Managing high-pressure production outages where guessing leads to costly thrashing

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add noeljackson/agentic systematic-debugging

For use in Claude.ai and ChatGPT

主要功能

01Provides specialized diagnostic instrumentation for multi-component system boundaries

020 GitHub stars

03Enforces the 'Iron Law' of no fixes without completed root cause investigation

04Guides backward data flow tracing to find the original trigger of deep call stack errors

05Mandates the creation of a failing test case before any implementation phase begins

06Implements a 3-fix limit that triggers mandatory architectural review if issues persist

使用场景

01Resolving deep logic errors where the symptom appears far from the actual bug source

02Debugging intermittent failures in complex CI/CD pipelines or distributed systems

03Managing high-pressure production outages where guessing leads to costly thrashing