{"enrichment":{"faq":[{"a":"Systematic Debugging enforces a 4-phase pipeline: evidence gathering (collect logs, stack traces, reproduction steps), pattern comparison (identify what changed), hypothesis testing (isolate the actual cause), and targeted fixes (apply only after root cause is confirmed). This prevents surface-level patches that mask underlying issues and works across test failures, production bugs, performance problems, and build failures on any tech stack.","q":"How to debug a bug systematically with Systematic Debugging?"},{"a":"Systematic Debugging treats test failures by first gathering evidence\u2014the exact failure output, preceding test state, and reproduction conditions. Then compare patterns: did this test pass before, and what changed? Form hypotheses about the actual cause rather than the symptom. Only after confirming the root cause does Systematic Debugging guide you to write a regression test and apply the fix, ensuring the bug won't resurface.","q":"What's the root cause analysis process for test failures?"},{"a":"Systematic Debugging traces data flow by mapping each layer's input and output during evidence gathering. Compare patterns across components to pinpoint where corruption begins. Test hypotheses by instrumenting checkpoints between layers. This structured approach isolates whether bad data comes from an upstream service, a transformation step, or a database query\u2014not just where it's observed.","q":"How do I find where bad data originates in a multi-component system?"},{"a":"Systematic Debugging raises architectural concerns when the evidence-gathering and pattern-comparison phases reveal that independent fixes all fail. This signals the root cause isn't in individual components but in how they interact. Before applying more patches, hypothesis testing should examine the overall design: message ordering, state consistency, or coupling assumptions that no single fix can address.","q":"When should I question architecture if multiple fixes fail independently?"},{"a":"Systematic Debugging applies its 4-phase pipeline to CI failures: gather full build logs and environment state, compare against passing builds to spot differences, form hypotheses about whether the issue is flaky infrastructure, dependency changes, or code logic, then verify the root cause before fixing. This prevents chase-the-symptom cycles and creates regression tests to catch the failure again.","q":"How does Systematic Debugging help debug CI build failures?"},{"a":"Systematic Debugging enforces root-cause investigation before any code changes, preventing the common failure of applying patches that hide deeper issues. By following evidence gathering, pattern comparison, and hypothesis testing, you discover why code behaves unexpectedly rather than where it breaks. This discipline works across any tech stack and ensures fixes are durable, not temporary masks.","q":"What makes Systematic Debugging different from just fixing the symptom?"}],"shadow_tags":["root-cause-analysis","investigative-debugging","multi-phase-workflow","data-flow-tracing","hypothesis-testing","regression-prevention","evidence-gathering","symptom-vs-cause","test-driven-fix","architectural-questioning"],"summary_rewrite":"Systematic Debugging enforces disciplined root-cause investigation before any code changes, using a 4-phase pipeline: evidence gathering, pattern comparison, hypothesis testing, and targeted fixes. It prevents the common failure mode of applying surface-level patches that mask underlying issues. Works with test failures, production bugs, performance problems, and build failures across any tech stack."},"files":[{"bytes":14043,"path":"superpowers/skills/systematic-debugging/SKILL.md","sha256":"3133187d058389665362162ab27f77b141e7be2494f7f0233840dfbde9eb5e77","url":"https://skillfed.io/files/FradSer/dotclaude/systematic-debugging/328b515a/SKILL.md"}],"id":"FradSer/dotclaude/systematic-debugging","links":{"html":"https://skillfed.io/FradSer/dotclaude/systematic-debugging","md":"https://skillfed.io/FradSer/dotclaude/systematic-debugging.md","repo":"https://github.com/FradSer/dotclaude"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":47,"language":"JavaScript","last_updated":"2026-07-23","license":"MIT","name":"systematic-debugging","publisher":"FradSer","stars":576},"relations":{"categories":["debugging","quality-assurance","devops"],"similar":[{"id":"FradSer/dotclaude/brainstorming"},{"id":"Delphine-L/claude_global/systematic-debugging"},{"id":"FradSer/dotclaude/writing-plans"},{"id":"FradSer/dotclaude/executing-plans"},{"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"}]},"slug":{"owner":"FradSer","repo":"dotclaude","skill":"systematic-debugging"},"version":"328b515a"}