systematic-debugging

Investigate software bugs and test failures using hypothesis-driven root-cause analysis.

2|Updated Jul 11, 2024
One-click install
npx skills add https://github.com/nicograef/handbook --skill systematic-debugging-nicograef
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/nicograef/handbook/tree/main/.claude/skills/systematic-debugging
Command: npx skills add https://github.com/nicograef/handbook --skill systematic-debugging-nicograef

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents the common pitfall of guessing at code fixes by enforcing a rigorous, evidence-based investigation process that identifies the actual root cause of bugs and test failures before any code is modified.

Core Features & Use Cases

  • Evidence-Based Workflow: Guides the user through a 10-step process including reproduction, hypothesis formation, and verification.
  • Boundary Analysis: Provides specific techniques for tracing data flow across process and service boundaries to isolate where errors originate.
  • Use Case: When a CI pipeline fails with an intermittent error, use this Skill to systematically isolate the triggering conditions and verify the fix with a repeatable test case rather than applying speculative patches.

Quick Start

Use the systematic-debugging skill to investigate the failing test case in the current repository and identify the root cause.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
How do I find the root cause of intermittent test failures in a CI/CD pipeline?

To find the root cause of intermittent test failures, this approach enforces a systematic debugging workflow that reproduces the error, forms evidence-based hypotheses, and verifies fixes with repeatable test cases instead of applying speculative patches.

What is the best way to debug errors in distributed systems where symptoms are decoupled from their origins?

Debugging distributed systems requires boundary analysis to trace data flow across process and service boundaries, isolating exactly where errors originate before modifying any application logic or infrastructure code.

How do I systematically troubleshoot software bugs without guessing at code fixes?

Systematic troubleshooting uses an evidence-based, 10-step process that includes reproduction, hypothesis formation, and strict one-change-at-a-time verification to prevent guessing at code fixes and ensure reliable software maintenance.

Can I use hypothesis-driven testing to isolate triggering conditions for complex application logic errors?

Yes, hypothesis-driven testing isolates triggering conditions by enforcing strict one-change-at-a-time verification protocols, ensuring you accurately identify the root cause before applying any code modifications.

When should I not use a root-cause-first debugging approach for software maintenance?

You should avoid root-cause-first debugging when you need immediate, temporary patches for critical system outages, as this methodology prioritizes thorough evidence-based investigation and one-change-at-a-time verification over rapid deployment.