skills.rest
gusgad
gusgadCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Diagnose bugs through root cause investigation before proposing fixes.

1|Updated Jul 18, 2025
Search Tags:#software engineering#debugging#troubleshooting#root cause analysis#hypothesis testing#test failure
One-click install
npx skills add https://github.com/gusgad/service-agent-by-sap --skill systematic-debugging-gusgad
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/gusgad/service-agent-by-sap/tree/main/.agents/skills/superpowers/systematic-debugging
Command: npx skills add https://github.com/gusgad/service-agent-by-sap --skill systematic-debugging-gusgad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers often jump to quick fixes that only mask symptoms, leading to recurring bugs and wasted time. This Skill enforces a disciplined four-phase debugging process that finds the true root cause before any fix is attempted. ## Core Features & Use Cases - Root Cause Investigation: Read full error traces, reproduce issues consistently, check recent changes, and trace data flow backward to the source. - Hypothesis-Driven Testing: Form a single hypothesis, test it with the smallest possible change, and avoid stacking unverified fixes. - Architecture Escalation: After three failed fix attempts, stop patching and raise the architectural question explicitly. - Use Case: A test fails in a multi-component pipeline (client → API → database → Kafka consumer). Instead of guessing which layer broke, add diagnostic logging at each boundary, run once to locate the failure point, then investigate that specific component. ## Quick Start Use the systematic-debugging skill to investigate this failing test and find its root cause before suggesting 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 test failure systematically?▼

Start by reading the complete error message and stack trace, then reproduce the failure consistently. Check recent changes with git diff, form one hypothesis about the root cause, and test it with the smallest possible change before writing a fix.

How to find root cause in a multi-component system?▼

Add diagnostic logging at each component boundary showing what enters and leaves each component, then run once to see where the flow breaks. Investigate that specific component rather than guessing which layer is at fault.

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

Stop after three failed fix attempts on the same issue. Three or more failures indicate the architecture is the problem, not the fix, so raise the architectural question explicitly instead of attempting a fourth patch.

Why should I write a failing test before fixing a bug?▼

A failing test reproduces the bug and proves your fix actually addresses the root cause rather than just masking the symptom. An untested fix is only a guess that happened to make the symptom disappear once.

What are signs I am guessing instead of debugging?▼

Red flags include proposing fixes before tracing where bad values originated, changing several things at once, saying quick fix for now, and attempting one more fix after two have already failed.

Related Skills

Explore More Software Engineering Skills→
singhianand23045singhianand23045

investigate

Identify root causes of bugs through systematic four-phase investigation.

Community
Advanced
ceedaragentsceedaragents
794

debug

Diagnose bugs through failing-test reproduction, root cause analysis, and minimal targeted fixes.

Official
Intermediate
anderson-0anderson-0
4

verification

Require verification evidence before reporting software work as complete.

Community
Intermediate
justinsenseijustinsensei
1

runtime-debugging

Step through Python and Node.js code with breakpoints and inspection.

Community
Intermediate