{"enrichment":{"faq":[{"a":"Systematic Debugging guides you through a four-phase approach: first investigate the root cause by isolating what actually broke, then research external context to understand dependencies and recent changes, analyze patterns to spot recurring issues, and finally test hypotheses with minimal changes before implementing a full fix. This prevents the trap of patching symptoms without understanding the real problem.","q":"How do I debug a failing test systematically?"},{"a":"Systematic Debugging applies the same disciplined methodology to production troubleshooting: begin by gathering diagnostic evidence to pinpoint which system layer is failing, research the surrounding context and recent deployments, look for patterns in error logs and timing, then verify your hypothesis with a small test change before rolling out a full fix. This approach avoids repeated failed attempts.","q":"What's the Systematic Debugging process for production issues?"},{"a":"Systematic Debugging enforces questioning your architecture early and systematically tracing unexpected behavior through multiple components before attempting any repair. By investigating root cause first, researching context, analyzing patterns, and testing hypotheses with minimal changes, you gather the evidence needed to understand what broke and why\u2014eliminating guesswork and preventing the cycle of failed fix attempts.","q":"How does Systematic Debugging help me avoid guessing at fixes?"},{"a":"Systematic Debugging breaks the cycle by forcing you to investigate root cause before implementing fixes. Many failed attempts stem from patching symptoms rather than understanding the real problem. The skill's four-phase approach\u2014root cause investigation, context research, pattern analysis, and hypothesis testing\u2014ensures you've identified the actual failure point across your system layers before committing to a solution.","q":"Why do my fixes keep failing and how does Systematic Debugging help?"},{"a":"Systematic Debugging applies its disciplined methodology to flaky test failures by first investigating what conditions trigger the failure, researching external factors like timing or resource contention, analyzing patterns across test runs to spot intermittent behavior, and testing hypotheses with minimal test changes. This systematic tracing through multiple components reveals whether the issue lies in test setup, application code, or environmental factors.","q":"How does Systematic Debugging help debug flaky tests?"},{"a":"Systematic Debugging enforces a structured four-phase framework rather than ad-hoc patching: root cause investigation, external context research, pattern analysis, and hypothesis verification. This prevents wasted effort on symptoms, ensures you understand architecture before fixing, and gathers diagnostic evidence to pinpoint the actual failing layer. The MIT-licensed skill transforms debugging from guessing into disciplined problem-solving.","q":"What makes Systematic Debugging different from random troubleshooting?"}],"shadow_tags":["root-cause-analysis","troubleshooting-methodology","error-investigation","test-failure-diagnosis","evidence-gathering","hypothesis-validation","symptom-vs-cause","multi-layer-diagnostics","regression-prevention","architectural-assessment"],"summary_rewrite":"Systematic Debugging enforces a disciplined four-phase approach to troubleshooting: start with root cause investigation, then research external context, analyze patterns, and test hypotheses before implementing any fix. The skill prevents the common trap of patching symptoms, ensuring you understand what actually broke and why."},"files":[{"bytes":15313,"path":"superjawn/skills/systematic-debugging/SKILL.md","sha256":"53ebd1dcf1861d87468bedf1db59c29c46934bd18cefc4508fa506635bd7a54f","url":"https://skillfed.io/files/jamditis/claude-skills-journalism/systematic-debugging/9c41306d/SKILL.md"}],"id":"jamditis/claude-skills-journalism/systematic-debugging","links":{"html":"https://skillfed.io/jamditis/claude-skills-journalism/systematic-debugging","md":"https://skillfed.io/jamditis/claude-skills-journalism/systematic-debugging.md","repo":"https://github.com/jamditis/claude-skills-journalism"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":58,"language":"Python","last_updated":"2026-07-25","license":"MIT","name":"systematic-debugging","publisher":"jamditis","stars":342},"relations":{"categories":["debugging","quality-assurance","software-engineering"],"similar":[{"id":"Delphine-L/claude_global/systematic-debugging"},{"id":"obra/superpowers/systematic-debugging"},{"id":"getcrew44/crew44/systematic-debugging"},{"id":"rpamis/comet/systematic-debugging"},{"id":"beita6969/ScienceClaw/systematic-debugging"},{"id":"zernie/vigiles/systematic-debugging"},{"id":"xintaofei/codeg/systematic-debugging"},{"id":"guanyang/open-agent-hub/systematic-debugging"},{"id":"foryourhealth111-pixel/Vibe-Skills/systematic-debugging"},{"id":"ratacat/claude-skills/systematic-debugging"}]},"slug":{"owner":"jamditis","repo":"claude-skills-journalism","skill":"systematic-debugging"},"version":"9c41306d"}