{"enrichment":{"faq":[{"a":"systematic-debugging is a skill that enforces a disciplined methodology prioritizing root cause discovery over quick patches. Rather than applying fixes to visible symptoms, it guides you through four structured phases\u2014investigation, pattern analysis, hypothesis testing, and implementation\u2014ensuring each phase completes before advancing. This prevents the costly trap of symptom-fixing and reduces failed fix attempts.","q":"What is systematic-debugging and why does it matter?"},{"a":"systematic-debugging requires evidence gathering across component boundaries and data flow tracing before any fix attempt. Start by investigating what actually failed, then analyze patterns to distinguish root causes from symptoms. Trace data flow through your multi-component system to locate where failures originate, not where they surface. Only after identifying the true cause should you test and implement a fix.","q":"How do I find root cause not just symptoms when debugging?"},{"a":"systematic-debugging structures debugging into four sequential phases: investigation (gather facts about the failure), pattern analysis (identify what's actually broken), hypothesis testing (validate your theory before coding), and implementation (apply the fix). Complete each phase fully before moving to the next. This prevents jumping to solutions prematurely and ensures you're fixing root causes, not chasing symptoms.","q":"What is the four-phase debugging framework this skill teaches?"},{"a":"systematic-debugging addresses repeated fix failures by requiring you to trace data flow through multi-component systems and verify you've identified the actual root cause. When multiple fixes fail, the framework guides you to step back and re-examine whether you're fixing symptoms rather than causes. It also helps determine if an architectural refactor is needed versus continued targeted fixing.","q":"Why did my fix not work and how do I investigate?"},{"a":"systematic-debugging applies to production bugs by enforcing a methodical approach: investigate the failure conditions, analyze patterns across logs and components, form and test hypotheses about root cause, then implement fixes. This structured process works under time pressure by preventing wasted effort on symptom-fixes and ensuring you understand data flow before deploying changes.","q":"How do I debug production bugs step by step systematically?"},{"a":"systematic-debugging helps you determine if an architectural refactor is needed versus continued fixing by completing the four-phase process fully. If investigation and pattern analysis reveal systemic design issues rather than isolated bugs, or if multiple fix attempts fail despite proper root cause analysis, the framework signals that refactoring may be more efficient than continued patching.","q":"When should I stop trying fixes and consider refactoring instead?"}],"shadow_tags":["root-cause-analysis","troubleshooting-methodology","hypothesis-testing","data-flow-tracing","multi-layer-diagnostics","architectural-assessment","evidence-gathering","scientific-debugging","failure-pattern-recognition","systematic-investigation"],"summary_rewrite":"This skill enforces a disciplined debugging methodology that prioritizes root cause discovery over quick patches. Work through four phases\u2014investigation, pattern analysis, hypothesis testing, and implementation\u2014completing each before advancing. The framework prevents the trap of symptom-fixing by requiring evidence gathering across component boundaries and data flow tracing before any fix attempt."},"files":[{"bytes":9327,"path":"plugins/systematic-debugging/skills/systematic-debugging/SKILL.md","sha256":"5b911a04c63216ff14b27b6515f6d16ef01ecd5d6a95019de51cea172c15abd0","url":"https://skillfed.io/files/secondsky/claude-skills/systematic-debugging/d464139e/SKILL.md"}],"id":"secondsky/claude-skills/systematic-debugging","links":{"html":"https://skillfed.io/secondsky/claude-skills/systematic-debugging","md":"https://skillfed.io/secondsky/claude-skills/systematic-debugging.md","repo":"https://github.com/secondsky/claude-skills"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":29,"language":"TypeScript","last_updated":"2026-07-25","license":"MIT","name":"systematic-debugging","publisher":"secondsky","stars":196},"relations":{"categories":["debugging","software-engineering","quality-assurance"],"similar":[{"id":"obra/superpowers-skills/systematic-debugging"},{"id":"mrgoonie/claudekit-skills/systematic-debugging"},{"id":"mosif16/codex-Skills/systematic-debugging"},{"id":"NickCrew/Claude-Cortex/systematic-debugging"},{"id":"PracticalSwan/agent-skills/systematic-debugging"},{"id":"eyadsibai/ltk/systematic-debugging"},{"id":"ed3dai/ed3d-plugins/systematic-debugging"},{"id":"family3253/skill/superpowers-systematic-debugging"},{"id":"ratacat/claude-skills/systematic-debugging"},{"id":"ArcReel/ArcReel/systematic-debugging"}]},"slug":{"owner":"secondsky","repo":"claude-skills","skill":"systematic-debugging"},"version":"d464139e"}