systematic-debugging

Diagnoses bugs and test failures through structured four-phase root cause analysis.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/thedutchvisiongroup/agent-skills --skill systematic-debugging-thedutchvisiongroup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/thedutchvisiongroup/agent-skills/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/thedutchvisiongroup/agent-skills --skill systematic-debugging-thedutchvisiongroup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Random fixes and guess-and-check patching waste time, mask underlying issues, and introduce new bugs. This Skill enforces a disciplined root-cause-first debugging process so every fix addresses the actual problem instead of its symptoms. ## Core Features & Use Cases - Four-Phase Process: Guides investigation through root cause analysis, pattern comparison, hypothesis testing, and verified implementation, with mandatory checkpoints between phases. - Supporting Techniques: Includes reference guides for bisection (code and git bisect), root-cause tracing through call stacks, rubber duck debugging, defense-in-depth validation, time-boxed escalation, and post-fix documentation. - Agent Pitfall Guardrails: Catalogs common AI agent mistakes such as hallucinating root causes, overconfidence in first hypotheses, and proposing oversized refactors for simple bugs. - Use Case: A test suite fails after a dependency update. Instead of tweaking mocks repeatedly, the Skill walks you through reproducing the failure, bisecting recent commits with git bisect, forming a single testable hypothesis, and verifying the fix with a regression test. ## Quick Start Ask the AI to systematically debug the failing test or error you are seeing, starting with root cause investigation before proposing any fix.

Frequently Asked Questions about systematic-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a failing test systematically?

Start by reading the full error message and stack trace, then reproduce the failure consistently. Check recent changes with git diff or git log, isolate the failing component, and form one testable hypothesis before changing any code.

How to find which commit introduced a bug with git bisect?

Run git bisect start, mark the current commit as bad and a known working commit as good, then test each checked-out commit. You can automate it with git bisect run followed by your test command to find the first failing commit.

When should I not use a systematic debugging process?

Skip the full process for obvious typos, documented configuration drift, issues already pinpointed by a linter or type checker, and non-technical problems like requirement ambiguity. These have self-evident fixes that do not need investigation.

What should I do after three fix attempts have failed?

Stop attempting more fixes and question the architecture instead. Three or more failed fixes usually indicate a structural problem such as shared state or coupling, so discuss refactoring the pattern with the user rather than patching symptoms again.

Why do AI agents propose wrong fixes during debugging?

Common pitfalls include hallucinating root causes without evidence, overconfidence in the first hypothesis, fixing the wrong code path, and assuming code works without running it. Verifying hypotheses against actual code and output prevents these mistakes.