Why does this skill prevent immediate fixes?

Quick patches often mask symptoms without resolving the underlying issue, leading to technical debt and new bugs. This skill ensures stability by requiring evidence of the root cause first.

What happens if three or more fix attempts fail?

The process mandates a stop to question the fundamental architecture. It prevents 'thrashing' by encouraging a discussion on whether the design itself is flawed rather than just the code.

How does it handle complex, multi-component systems?

The skill uses specific diagnostic instrumentation at component boundaries (like API to Database) to log data entry/exit and verify environment propagation before proposing changes.

Does this skill work with Test-Driven Development?

Yes. Phase 4 requires the creation of a failing test case that reproduces the bug before any fix is implemented, ensuring the solution is verifiable and permanent.

Systematic Debugging

Name: Systematic Debugging
Author: jasir

byjasir

安全与测试

Enforces a rigorous, four-phase debugging methodology to identify root causes before proposing any software fixes.

关于

This skill transforms how Claude handles technical issues by enforcing the 'Iron Law': no fixes without prior root cause investigation. By guiding the AI through structured phases—Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation—it eliminates the time-wasting 'guess-and-check' cycle that leads to technical debt and regressive bugs. Whether dealing with complex CI/CD failures, distributed system issues, or simple logic errors, this skill ensures every fix is targeted, verified through test-driven development, and architecturally sound.

主要功能

Multi-component diagnostic instrumentation for tracing data across boundaries
Architectural review trigger that stops 'thrashing' after three failed fix attempts
Pattern analysis against working reference implementations to identify deviations
Mandatory root cause investigation phase before code modification
Backward data flow tracing to find the origin of deep-stack errors
0 GitHub stars

使用场景

Resolving deep-seated bugs in distributed, multi-layer microservices
Diagnosing intermittent test failures in complex CI/CD pipelines
Breaking cycles of regression where one fix introduces new issues elsewhere

关于

主要功能

Multi-component diagnostic instrumentation for tracing data across boundaries
Architectural review trigger that stops 'thrashing' after three failed fix attempts
Pattern analysis against working reference implementations to identify deviations
Mandatory root cause investigation phase before code modification
Backward data flow tracing to find the origin of deep-stack errors
0 GitHub stars

使用场景

Resolving deep-seated bugs in distributed, multi-layer microservices
Diagnosing intermittent test failures in complex CI/CD pipelines
Breaking cycles of regression where one fix introduces new issues elsewhere