Does this skill require writing automated tests?

Yes, Phase 4 requires creating a failing test case (or a one-off reproduction script) before implementing the fix to ensure the solution is verified and prevents future regressions.

How does this skill differ from standard bug fixing?

Standard fixing often involves 'guess-and-check' patches. This skill explicitly forbids proposing fixes until a root cause is proven through evidence, reproduction, and data flow analysis.

When should I use the Systematic Debugging skill?

Use it for any technical issue, especially complex test failures, production bugs, performance regressions, or when previous fix attempts have failed to solve the problem.

What happens if a fix doesn't work after several tries?

If three or more fixes fail, the skill mandates an architectural review. This helps determine if the underlying design pattern is flawed rather than just the specific implementation.

Can this skill help with issues in multi-component systems?

Yes, it includes specific protocols for adding diagnostic instrumentation at component boundaries to isolate exactly which layer of the stack is failing.

Systematic Debugging

Name: Systematic Debugging
Author: agi-house-india

byagi-house-india

セキュリティとテスト

Enforces a disciplined, four-phase approach to identifying and resolving root causes of software bugs and test failures.

概要

The Systematic Debugging skill transforms how Claude handles technical issues by mandating a root-cause-first methodology. Instead of applying quick patches that mask underlying problems, this skill guides Claude through evidence gathering, pattern analysis, and minimal hypothesis testing. It is particularly effective for complex multi-component systems, intermittent failures, and scenarios where previous fix attempts have failed, ensuring high-quality, architecturally-sound solutions over temporary workarounds.

主な機能

Mandatory four-phase debugging workflow from investigation to implementation
Strict requirement for failing test cases prior to implementation
Advanced diagnostic instrumentation for multi-component system boundaries
Backward data flow tracing to identify the origin of corrupted state
Architectural red flag detection for issues requiring more than three fix attempts
0 GitHub stars

ユースケース

Resolving persistent or intermittent test failures in CI/CD pipelines
Investigating production bugs where the root cause is hidden by environmental factors
Debugging complex data flow issues across multi-layered backend services

概要

主な機能

Mandatory four-phase debugging workflow from investigation to implementation
Strict requirement for failing test cases prior to implementation
Advanced diagnostic instrumentation for multi-component system boundaries
Backward data flow tracing to identify the origin of corrupted state
Architectural red flag detection for issues requiring more than three fix attempts
0 GitHub stars

ユースケース

Resolving persistent or intermittent test failures in CI/CD pipelines
Investigating production bugs where the root cause is hidden by environmental factors
Debugging complex data flow issues across multi-layered backend services