Investigate technical issues through four phases to identify root causes.
npx skills add https://github.com/jmmL/dr3-old --skill systematic-debugging-jmml
Please help me install this Agent Skill. Skill: systematic-debugging Source: https://github.com/jmmL/dr3-old/tree/main/.claude/skills/systematic-debugging Command: npx skills add https://github.com/jmmL/dr3-old --skill systematic-debugging-jmml
This skill provides a structured approach to debugging that ensures you identify the root cause before proposing fixes.
Use this skill to guide a debugging session when you encounter a bug, test failure, or unexpected behavior, and ensure you follow the four-phase process before proposing fixes.
High-intent search queries and answers about installing and using this skill.
Systematic debugging is a structured approach that enforces phase-driven investigation to identify the root cause before proposing fixes. It stops symptom fixes by requiring evidence-based pattern analysis and hypothesis testing to address the original trigger.
To find the root cause, follow a four-phase investigation process: root cause investigation, pattern analysis, hypothesis testing, and implementation. This ensures you systematically uncover the root cause through evidence rather than applying immediate patches.
The best way to investigate unexpected behavior is using a defense-in-depth approach with multiple validation layers and explicit anti-patterns. This method resists shortcuts and ensures you validate the root cause through structured hypothesis testing.
Yes, systematic debugging applies to any technical issue, including build failures, performance problems, test failures, and production faults. It adapts to any scenario where evidence-based root-cause analysis is needed.
Structure your debugging session using four mandatory phases: root cause investigation, pattern analysis, hypothesis testing, and implementation. This framework enforces systematic investigation and includes explicit anti-patterns to resist premature fixes.
Root-cause tracing should not be used when you need an immediate, temporary patch to restore service and lack the time for evidence-based pattern analysis. It is designed for systematic investigation, not quick symptom suppression.
seanGSISGDiagnose software bug root causes through four investigation phases.
h4v1dTrace call stacks to identify the original trigger behind failures.
FelixBitSoulIdentify and resolve root causes of bugs and failing tests.
leonanpereirapintoEnforce root-cause fixes by detecting and rejecting workaround patterns in code.
