skills.rest
JuanMS20
JuanMS20COMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Identify software failure root causes through a four-phase debugging framework.

Updated May 3, 2026
Search Tags:#debugging#methodology#investigation#troubleshooting#systematic#root-cause#software-engineering
One-click install
npx skills add https://github.com/JuanMS20/solviora-agent --skill systematic-debugging-juanms20
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/JuanMS20/solviora-agent/tree/main/skills/software-development/systematic-debugging
Command: npx skills add https://github.com/JuanMS20/solviora-agent --skill systematic-debugging-juanms20

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Root cause debugging is often approached via patchwork fixes that waste time and propagate issues. This skill provides a disciplined framework to uncover the true cause before attempting fixes, reducing rework and improving stability.

Core Features & Use Cases

  • Four-phase debugging process: read errors, reproduce reliably, trace data flow, and gather evidence before any fix.
  • Structured pattern analysis, hypothesis testing, and controlled implementation to prevent regression.
  • Suitable for software bugs, production incidents, flaky tests, and complex integration failures.

Quick Start

Follow the four phases in order to identify root cause before implementing any fixes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is a systematic approach to debugging software failures?▼

Systematic debugging identifies root causes through a structured four-phase framework: reading errors, reproducing reliably, tracing data flow, and gathering evidence before attempting fixes.

How do I find the root cause of a production incident instead of applying patchwork fixes?▼

Find root causes of production incidents by applying deterministic analysis with explicit data-gathering steps and hypothesis testing to ensure verifiable outcomes before implementing controlled fixes.

What is the best way to troubleshoot flaky tests and complex integration failures?▼

Troubleshoot flaky tests and integration failures using structured pattern analysis and controlled implementation to reproduce reliably and trace data flow, preventing regression and improving stability.

Can I use this debugging methodology for any codebase or service?▼

Apply this debugging methodology across codebases, services, and integrations for bug investigations, production incidents, test failures, and flaky behavior without requiring external dependencies.

When should I not use a structured debugging framework?▼

Avoid structured debugging when a patchwork fix is sufficient, though note that skipping root cause investigation and explicit data-gathering steps often wastes time and propagates issues.

How do I start a root cause investigation for a bug?▼

Start a root cause investigation by following the four phases in order: read errors, reproduce reliably, trace data flow, and gather evidence to identify the true cause before implementing any fixes.

Related Skills

Explore More Software Engineering Skills→
derHakenderHaken
437

systematic-debugging

Trace data flow and apply a four-phase process to fix root causes.

Community
Advanced
cosmixcosmix
53

debugging

Diagnose and resolve software bugs across programming languages and environments.

Community
Intermediate
Jiachen-T-WangJiachen-T-Wang

research

Facilitate LLM research workflows for experiment replication and training log analysis.

Community
Advanced
writerwriter
6

Shrinkage Risk Detector

Analyze inventory variance and POS exceptions to identify high-risk retail locations.

Official
Advanced