skills.rest
drvoss
drvossCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Diagnose software bugs with a four-phase root cause analysis.

42|9|Updated Mar 16, 2026
Search Tags:#git#testing#debugging#troubleshooting#root cause analysis#reproducibility#regression-testing
One-click install
npx skills add https://github.com/drvoss/everything-copilot-cli --skill systematic-debugging-drvoss
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/drvoss/everything-copilot-cli/tree/main/skills/development/systematic-debugging
Command: npx skills add https://github.com/drvoss/everything-copilot-cli --skill systematic-debugging-drvoss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a disciplined four-phase root cause analysis to diagnose and permanently resolve non-obvious, intermittent, or environment-specific software bugs that resist quick fixes and often return when only symptoms are patched.

Core Features & Use Cases

  • Reproducibility: Prioritizes creating a deterministic failing test or input to reproduce the bug on demand.
  • System understanding: Guides engineers to trace code paths, verify assumptions, and collect precise evidence before changing behavior.
  • Hypothesis-driven verification: Encourages single-hypothesis tests with minimal, targeted changes to confirm or falsify causes.
  • Fix and prevention: Ensures root-cause fixes, adds regression tests, documents the root cause in commit messages, and escalates to architecture review when needed.
  • Use Case: Ideal for intermittent production failures, bugs appearing only in specific environments, or regressions that recur after naive fixes.

Quick Start

Create a minimal failing test that reproduces the bug, form and test a single hypothesis with a targeted change, then implement the root-cause fix with a regression test and a clear commit message.

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 an intermittent bug that keeps recurring in production?▼

Intermittent bugs resist quick fixes because they only patch symptoms. A structured root cause analysis resolves them by creating a reproducible test case, verifying assumptions through hypothesis-driven testing, and implementing a targeted fix with regression test coverage.

What is the best way to debug environment-specific software failures?▼

The best way to debug environment-specific failures is to trace code paths and verify system assumptions to collect precise evidence. Form a single hypothesis about the discrepancy, test it with a minimal change, and document the root cause in your commit message.

How do I create a reproducible test case for a non-obvious software bug?▼

Creating a reproducible test case for a non-obvious bug requires prioritizing deterministic inputs. Build a minimal failing test that reliably triggers the defect on demand, allowing you to iteratively verify hypotheses and confirm the root cause before applying fixes.

Does systematic debugging work for regressions that reappear after naive fixes?▼

Yes, systematic debugging specifically targets regressions that reappear after naive fixes. It enforces a four-phase process requiring regression test coverage and documented commit messages, ensuring the underlying root cause is permanently resolved rather than temporarily patched.

When should I escalate a stubborn bug to an architecture review?▼

You should escalate a stubborn bug to an architecture review when the root cause analysis indicates a fundamental design flaw. If hypothesis-driven verification proves the issue stems from structural limitations rather than isolated logic errors, architectural changes are needed to prevent recurrence.

Related Skills

Explore More Software Engineering Skills→
santosomarsantosomar
1

test-case-reducer

Reduce large failing test inputs to minimal forms using delta debugging.

Community
Intermediate
aist-ai-sastaist-ai-sast

mcp-regression-fix

Diagnose MCP regression failures and implement durable fixes across test suites.

Official
Advanced
cosmixcosmix
53

debugging

Diagnose and resolve software bugs across programming languages and environments.

Community
Intermediate
farsinkfarsink

systematic-debugging

Guide software debugging through a four-phase root cause analysis process.

Community
Advanced