skills.rest
russosalv
russosalvCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Enforce root cause investigation with evidence gathering before applying fixes.

5|Updated Apr 18, 2026
Search Tags:#testing#debugging#investigation#root cause#defense-in-depth#triage#flaky-tests
One-click install
npx skills add https://github.com/russosalv/NONoise --skill systematic-debugging-russosalv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/russosalv/NONoise/tree/main/packages/skills/vendor/superpowers/skills/systematic-debugging
Command: npx skills add https://github.com/russosalv/NONoise --skill systematic-debugging-russosalv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Random, surface-level fixes waste time and introduce new bugs by addressing symptoms instead of causes. This Skill enforces a structured, four-phase process so engineers reproduce issues, gather evidence, and only apply minimal, verified changes that resolve the root cause.

Core Features & Use Cases

  • Four-phase workflow: Root cause investigation, pattern analysis, hypothesis and testing, then guarded implementation with a failing test.
  • Evidence-first diagnostics: Guided steps for reproducibility, multi-component instrumentation, and backward call-stack tracing to locate the original trigger.
  • Safety & guardrails: Single-hypothesis testing, limits on consecutive fixes, defense-in-depth validation, and escalation guidance when architecture is at fault.
  • Practical tools: Example scripts and utilities for condition-based waiting, bisection of polluting tests, and concrete test-case creation patterns for flaky CI and production incidents.

Quick Start

Use the systematic-debugging skill to run a four-phase investigation, gather reproducible evidence, form a single hypothesis, and create a minimal failing test before applying 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 find the root cause of a software bug before attempting a fix?▼

To find the root cause of a software bug, use a four-phase investigation workflow: gather reproducible evidence, analyze patterns, form a single hypothesis, and create a minimal failing test before applying any fix.

What is the best way to debug flaky CI tests and integration errors?▼

Debug flaky CI tests using evidence-first diagnostics with multi-component instrumentation, backward call-stack tracing, and bisection of polluting tests to locate the original trigger and establish reproducibility.

How do I investigate production incidents in multi-component systems?▼

Investigate production incidents in multi-component systems by enforcing stepwise root cause investigation. Gather reproducible evidence, test a single hypothesis, and apply minimal verified changes with defense-in-depth validation.

Why do my random bug fixes introduce new unexpected behaviors?▼

Random bug fixes introduce new unexpected behaviors because they address symptoms instead of causes. Applying minimal, verified changes based on a single tested hypothesis prevents introducing new regressions.

When should I escalate a debugging investigation instead of applying another fix?▼

Escalate a debugging investigation when the architecture is at fault. The process includes limits on consecutive fixes and escalation guidance to prevent compounding errors when the system design itself causes the unexpected behavior.

Related Skills

Explore More Software Engineering Skills→
Khoatran1999Khoatran1999

Root Cause Tracing

Trace bugs backward through call stacks to locate original triggers.

Community
Advanced
dmulcaheydmulcahey

systematic-debugging

Trace software bugs to root causes using a four-phase investigation methodology.

Community
Advanced
benjgradbenjgrad

systematic-debugging

Diagnose software bugs through four non-skippable root-cause investigation phases.

Community
Advanced
ArtRivArtRiv

gsd-debug

Diagnose software issues by gathering symptoms and running structured root-cause investigations.

Community
Advanced