What problem does it solve?
This Skill prevents wasted time and the introduction of new bugs by enforcing a rigorous, systematic approach to debugging, ensuring that the root cause of any issue is identified and understood before any fixes are attempted.
Core Features & Use Cases
- Root Cause Analysis: Guides users through careful error message analysis, consistent reproduction steps, and evidence gathering in multi-component systems.
- Pattern Identification: Helps users find working examples, compare against references, and identify critical differences.
- Hypothesis Testing: Promotes the scientific method by forming single hypotheses and testing them with minimal, isolated changes.
- Architectural Questioning: Provides a framework to question the underlying architecture when multiple fixes fail, preventing endless symptom-fixing.
- Use Case: When a CI build fails unexpectedly, instead of randomly tweaking build scripts, this Skill ensures you first meticulously gather logs, trace data flow, and identify the exact component or configuration causing the failure before proposing any changes.
Quick Start
Use the systematic-debugging skill to investigate the root cause of the recent test failure.
