Can this skill help with microservices?

Yes, it includes specific protocols for gathering evidence at component boundaries to identify exactly which layer of a distributed system is failing.

When should I use the architectural review phase?

The skill automatically triggers an architectural review if three consecutive fix attempts fail, indicating that the problem may be a fundamental design flaw rather than a simple bug.

Does this skill work with automated testing?

Yes, it requires creating a failing test case in Phase 4 to verify the fix and prevent future regressions, integrating directly with TDD practices.

What is the 'Iron Law' of systematic debugging?

The Iron Law states that no fixes can be proposed or implemented until a thorough Root Cause Investigation (Phase 1) is completed and the 'why' behind the bug is understood.

How does this skill improve debugging speed?

While it requires more upfront analysis, it eliminates 'thrashing'—the cycle of applying and reverting incorrect fixes—which typically reduces total resolution time from hours to minutes.

Systematic Debugging

Name: Systematic Debugging
Author: kivilaid

bykivilaid

•

安全与测试

Enforces a rigorous four-phase framework to identify root causes and eliminate guess-and-check thrashing during the software debugging process.

关于

The Systematic Debugging skill transforms how technical issues are resolved by mandating a structured, investigation-first approach. Instead of applying quick patches that mask underlying issues, this skill guides the developer through Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation. It is specifically designed to handle complex multi-component systems, intermittent failures, and high-pressure production bugs by enforcing 'The Iron Law': no fixes without a verified root cause. By integrating with test-driven development and data flow tracing, it ensures that every fix is permanent and doesn't introduce regressions.

主要功能

Mandatory root cause verification before proposing any code changes
Multi-component diagnostic instrumentation for tracing data across boundaries
6 GitHub stars
Architectural safety valve that triggers review after three failed fix attempts
Seamless integration with TDD and root-cause-tracing sub-skills
Four-phase framework: Investigation, Analysis, Hypothesis, and Implementation

使用场景

Resolving intermittent test failures or production bugs that defy obvious explanation
Debugging complex data flow issues across microservices or multi-layered architectures
Breaking out of 'debugging loops' where previous fixes have failed or caused new issues

关于

主要功能

Mandatory root cause verification before proposing any code changes
Multi-component diagnostic instrumentation for tracing data across boundaries
6 GitHub stars
Architectural safety valve that triggers review after three failed fix attempts
Seamless integration with TDD and root-cause-tracing sub-skills
Four-phase framework: Investigation, Analysis, Hypothesis, and Implementation

使用场景

Resolving intermittent test failures or production bugs that defy obvious explanation
Debugging complex data flow issues across microservices or multi-layered architectures
Breaking out of 'debugging loops' where previous fixes have failed or caused new issues