{"enrichment":{"faq":[{"a":"Systematic-debugging is a disciplined process that enforces root cause investigation before attempting any fix. Rather than patching symptoms, it establishes a tight feedback loop to reproduce the exact failure, gathers evidence across system boundaries, traces data flow to its source, and forms testable hypotheses. This approach eliminates guesswork and prevents quick fixes from masking deeper issues that will resurface later.","q":"What is systematic-debugging and why does it matter?"},{"a":"Systematic-debugging prioritizes creating a tight feedback loop that reproduces the exact symptom consistently. Start by documenting the precise conditions when the failure occurs, isolate variables one at a time, and build a minimal test case that triggers the problem reliably. This reproducibility is foundational\u2014without it, you cannot confidently verify whether your fix actually addresses the root cause or merely hides the symptom temporarily.","q":"How do I establish a reproducible test case for a failing behavior?"},{"a":"Systematic-debugging structures debugging into four sequential phases: root cause investigation (gather evidence across system boundaries), pattern analysis (identify what conditions trigger the failure), hypothesis testing (form and validate testable theories about the source), and verification (confirm the fix resolves the actual problem, not just the symptom). Completing each phase in order prevents wasted effort on symptom fixes that mask real issues.","q":"What is the debugging process systematic-debugging recommends?"},{"a":"Systematic-debugging emphasizes systematically narrowing down where a problem originates by tracing data flow to its source. Follow inputs through your system, log state at each boundary, and identify where values diverge from expected behavior. This methodical approach reveals the actual point of failure rather than where symptoms become visible, enabling you to address root causes instead of downstream effects.","q":"How can I trace data flow in code to find where problems originate?"},{"a":"Systematic-debugging tackles flaky tests by establishing reproducible conditions and gathering comprehensive evidence. Identify environmental factors, timing dependencies, and state interactions that trigger intermittent failures. Use hypothesis testing to isolate which component or interaction is responsible, then verify your fix eliminates the flakiness rather than just reducing its frequency. This scientific approach replaces guessing with confidence.","q":"How do I debug flaky or intermittent failures with higher confidence?"},{"a":"Systematic-debugging prevents recurring failures by avoiding quick patches that mask real issues. Before implementing any fix, complete root cause investigation and hypothesis testing phases. Verify that your proposed solution addresses the actual problem source, not just the symptom. This disciplined workflow ensures fixes stick and prevents the cycle of temporary patches that create technical debt and future failures.","q":"Why do my fixes keep failing and how do I avoid that?"}],"shadow_tags":["root-cause-analysis","troubleshooting-methodology","bug-investigation","reproducibility","hypothesis-testing","diagnostic-process","regression-prevention","data-flow-tracing","feedback-loop"],"summary_rewrite":"This skill enforces a disciplined debugging process: establish a tight feedback loop that reproduces the exact symptom, gather evidence across system boundaries, trace data flow to its source, and form testable hypotheses before proposing any fix. By completing each phase sequentially\u2014root cause investigation, pattern analysis, hypothesis testing, and verification\u2014you eliminate guesswork and prevent quick patches from masking deeper issues."},"files":[{"bytes":14065,"path":"skills/software-development/systematic-debugging/SKILL.md","sha256":"ec6c97b1d5534a86328ded47e607a7cfb797629ddb1eb842b9a36b298c4b76d3","url":"https://skillfed.io/files/NousResearch/hermes-agent/systematic-debugging/dfc8653d/SKILL.md"}],"id":"NousResearch/hermes-agent/systematic-debugging","links":{"html":"https://skillfed.io/NousResearch/hermes-agent/systematic-debugging","md":"https://skillfed.io/NousResearch/hermes-agent/systematic-debugging.md","repo":"https://github.com/NousResearch/hermes-agent"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":42317,"language":"Python","last_updated":"2026-07-28","license":"MIT","name":"systematic-debugging","publisher":"NousResearch","stars":221503},"relations":{"categories":["debugging","quality-assurance","software-development"],"similar":[{"id":"mateaix/mateclaw/systematic-debugging"},{"id":"moltis-org/moltis/systematic-debugging"},{"id":"graniet/kheish/systematic-debugging"},{"id":"vinvcn/mattpocock-skills-zh-CN/diagnosing-bugs"},{"id":"mattpocock/skills/diagnosing-bugs"},{"id":"ArcReel/ArcReel/diagnosing-bugs"},{"id":"mxyhi/ok-skills/diagnosing-bugs"},{"id":"sammcj/agentic-coding/diagnose-hard-problem"},{"id":"jamditis/claude-skills-journalism/systematic-debugging"},{"id":"PracticalSwan/agent-skills/systematic-debugging"}]},"slug":{"owner":"NousResearch","repo":"hermes-agent","skill":"systematic-debugging"},"version":"dfc8653d"}