{"enrichment":{"faq":[{"a":"debug-systematic provides a 4-phase protocol for investigating complex, intermittent, or mysterious bugs. The framework guides you through reproducing issues reliably, narrowing scope to the failing component using techniques like binary search and git bisect, understanding root causes through the scientific method, and implementing minimal fixes with regression tests. This disciplined, evidence-based approach eliminates guesswork and ensures you address the actual problem, not just symptoms.","q":"How to debug complex bugs systematically?"},{"a":"debug-systematic's 4-phase protocol structures bug investigation into: (1) establishing reliable reproduction steps and environment documentation, (2) narrowing down bug location and isolating root cause in large codebases using binary search and git bisect, (3) applying the scientific method to diagnose why bugs occur, not just where they are, and (4) preventing regressions by writing tests and avoiding common debugging anti-patterns. This systematic approach transforms mysterious failures into solvable problems.","q":"What is the 4 phase debugging methodology?"},{"a":"debug-systematic teaches you to isolate intermittent bugs by first establishing reliable reproduction steps and documenting your environment. Then narrow down the bug location in large codebases using binary search and git bisect to pinpoint when the failure was introduced. Apply the scientific method to diagnose why the bug occurs, not just where it is. Finally, write regression tests to prevent the issue from recurring and avoid common debugging anti-patterns that mask root causes.","q":"How can I find the root cause of intermittent failures?"},{"a":"debug-systematic emphasizes using binary search and git bisect to efficiently isolate failing components in large codebases. These techniques let you quickly identify which commit introduced the regression without manually inspecting thousands of lines. Combined with reliable reproduction steps, you can systematically eliminate half the search space with each iteration. This disciplined approach prevents the common pitfall of random code inspection and ensures you locate the actual source of the problem.","q":"How do I narrow down bug location in large codebases?"},{"a":"debug-systematic helps you prevent regressions by identifying and avoiding common debugging anti-patterns. The framework emphasizes establishing reliable reproduction steps before diving into code, using the scientific method instead of guesswork, and writing tests to catch future regressions. By following the 4-phase protocol and avoiding shortcuts like random code changes or environment-specific fixes, you ensure your solutions address root causes and don't create new bugs.","q":"What debugging anti-patterns should I avoid?"},{"a":"debug-systematic teaches you to diagnose why bugs occur, not just where they are, by applying the scientific method to bug investigation. This means forming hypotheses about root causes, designing tests to validate or refute them, and gathering evidence before implementing fixes. This evidence-based approach transforms debugging from trial-and-error guesswork into disciplined problem-solving, ensuring you understand the actual mechanism behind failures and implement minimal, targeted fixes.","q":"How does debug-systematic apply the scientific method?"}],"shadow_tags":["root-cause-analysis","troubleshooting-methodology","regression-detection","intermittent-failures","evidence-based-debugging","binary-search-technique","reproduction-steps","diagnostic-protocol","anti-pattern-prevention"],"summary_rewrite":"A disciplined, evidence-based debugging framework that walks you through reproducing issues reliably, narrowing scope to the failing component, understanding root causes through the scientific method, and implementing minimal fixes with regression tests. Eliminates guesswork and ensures you address the actual problem, not just symptoms."},"files":[{"bytes":5375,"path":"skills/debug-systematic/SKILL.md","sha256":"861e2bddc83e39f65bbc71c45b8b5219ea41b4fedc51f08b49bc96adc0ad4f98","url":"https://skillfed.io/files/travisjneuman/.claude/debug-systematic/86d09d9d/SKILL.md"}],"id":"travisjneuman/.claude/debug-systematic","links":{"html":"https://skillfed.io/travisjneuman/.claude/debug-systematic","md":"https://skillfed.io/travisjneuman/.claude/debug-systematic.md","repo":"https://github.com/travisjneuman/.claude"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":20,"language":"JavaScript","last_updated":"2026-07-17","license":"MIT","name":"debug-systematic","publisher":"travisjneuman","stars":85},"relations":{"categories":["debugging","software-engineering","quality-assurance"],"similar":[{"id":"spencerpauly/awesome-cursor-skills/systematic-debugging"},{"id":"itzzritik/OrderWorder/systematic-debugging"},{"id":"Mathews-Tom/armory/debug-investigator"},{"id":"vudovn/ag-kit/systematic-debugging"},{"id":"wshobson/agents/debugging-strategies"},{"id":"sangrokjung/claude-forge/debugging-strategies"},{"id":"HermeticOrmus/LibreUIUX-Claude-Code/debugging-strategies"},{"id":"bobmatnyc/claude-mpm-skills/systematic-debugging"},{"id":"ctsstc/get-shit-done-skills/debugger"},{"id":"Jeffallan/claude-skills/debugging-wizard"}]},"slug":{"owner":"travisjneuman","repo":".claude","skill":"debug-systematic"},"version":"86d09d9d"}