systematic-debugging

Diagnose bugs and test failures through a four-phase root cause investigation process.

1|Updated Mar 12, 2026

Search Tags:#debugging #investigation #troubleshooting #pytest #root cause analysis #test failures #regression testing

Ready to run

npx skills add https://github.com/kaminocorp/hermes-alpha-hunter --skill systematic-debugging-kaminocorp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/kaminocorp/hermes-alpha-hunter/tree/main/skills/software-development/systematic-debugging
Command: npx skills add https://github.com/kaminocorp/hermes-alpha-hunter --skill systematic-debugging-kaminocorp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Random fixes and guess-and-check patching waste hours and introduce new bugs. This Skill enforces a disciplined four-phase debugging methodology that finds the root cause before any fix is attempted, preventing symptom-patching and repeated failed fix attempts. ## Core Features & Use Cases - Four-Phase Investigation: Structured workflow covering root cause investigation, pattern analysis, hypothesis testing, and verified implementation. - Rule of Three: After three failed fix attempts, the process stops and questions the underlying architecture instead of attempting a fourth patch. - Red Flag Detection: Identifies rationalizations like "quick fix for now" and forces a return to systematic investigation. - Use Case: A failing pytest suite in production gets traced through error messages, git history, and data flow analysis to isolate the exact component at fault, then fixed with a regression test proving the fix. ## Quick Start Use the systematic-debugging skill to investigate why my test suite is failing and find the root cause 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 with pytest. Check recent git changes, trace the data flow to find where the bad value originates, and only then form a hypothesis and test it with a minimal change.

What is root cause analysis in debugging?▼

Root cause analysis means identifying why a bug happens before attempting any fix, rather than patching symptoms. This Skill enforces it through four phases: investigation, pattern analysis, hypothesis testing, and verified implementation with a regression test.

When should I stop trying fixes and reconsider the architecture?▼

Stop after three failed fix attempts. If each fix reveals new problems in different places or requires massive refactoring, the pattern indicates an architectural problem that should be discussed before attempting more fixes.

Can systematic debugging work under time pressure?▼

Yes, and it is especially recommended under time pressure. Systematic investigation typically resolves bugs in 15-30 minutes, while random guess-and-check fixing often takes hours of thrashing and introduces new bugs.

Why do quick fixes cause more bugs?▼

Quick fixes address symptoms rather than root causes, so the underlying issue persists and resurfaces elsewhere. Bundling multiple changes at once also makes it impossible to isolate what worked, frequently introducing new defects.