skills.rest
wesleysimplicio
wesleysimplicioCOMMUNITY
Explore all skills by this author →
𝕏@wesleysimplicGitHub

systematic-debugging

Trace root causes through a four-phase debugging workflow.

1|Updated May 7, 2026
Search Tags:#debugging#defense-in-depth#root-cause#software-engineering#issue-tracing#systematic-debugging
One-click install
npx skills add https://github.com/wesleysimplicio/simplicio-mapper --skill systematic-debugging-wesleysimplicio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/wesleysimplicio/simplicio-mapper/tree/main/.skills/systematic-debugging
Command: npx skills add https://github.com/wesleysimplicio/simplicio-mapper --skill systematic-debugging-wesleysimplicio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Root causes drive reliable fixes; without a systematic approach, teams chase symptoms and waste time on rework. By structuring investigation, pattern analysis, and validation, it helps teams reproduce issues reliably, understand data flow, and implement durable fixes.

Core Features & Use Cases

  • Phase 1: Root Cause Investigation — read error messages carefully, reproduce consistently, check recent changes, and trace data flow to identify the source.
  • Phase 2: Pattern Analysis — find working examples, compare against references, identify differences, and understand dependencies.
  • Phase 3: Hypothesis and Testing — form a single hypothesis, test minimally with controlled changes, verify results, and decide next steps.
  • Phase 4: Implementation — create failing tests, implement the root-cause fix, and verify across affected components.
  • Defense-in-Depth: validate data at entry points, business logic, environment guards, and instrumentation to prevent regression.
  • Supporting techniques: root-cause-tracing.md, defense-in-depth.md, condition-based-waiting.md.

Quick Start

Begin with Phase 1: reproduce the issue, read error messages, and trace data flow to identify the root cause.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is the best way to find a software bug's root cause before fixing it?▼

Systematic debugging identifies root causes by reproducing issues consistently, reading error messages carefully, and tracing data flow to find the source before implementing any fixes.

How do I debug production bugs and test failures in multi-component systems?▼

Debugging multi-component systems uses a phase-driven workflow: investigate root causes, analyze patterns against working examples, test a single hypothesis with minimal changes, then implement and verify the fix.

What's the best way to systematically debug software instead of guessing fixes?▼

Systematic debugging enforces four phases: root-cause investigation, pattern analysis, hypothesis testing, and implementation. You form a single hypothesis, test minimally with controlled changes, and verify results before proceeding.

Can I use a systematic debugging workflow for performance issues and integration problems?▼

Yes, this debugging workflow applies across software projects for performance issues, integration problems, test failures, and production bugs. It traces root causes using pattern analysis and data flow investigation regardless of issue type.

How do I prevent regression after fixing a software bug?▼

Prevent regression using defense-in-depth: validate data at entry points, enforce business logic guards, add environment checks, and implement stack-trace instrumentation. Create failing tests first, then implement the root-cause fix.

Related Skills

Explore More Software Engineering Skills→
JuniYadiJuniYadi

issue-parser

Parse GitHub issue titles and bodies to extract errors, file paths, and function names.

Community
Intermediate
ucirelloucirello
2

defense-in-depth

Implement multi-layer data validation across entry points, business logic, environment guards, and debug instrumentation.

Community
Advanced
withzombieswithzombies
80

fixing-bugs

Automate bug fixing from issue creation through regression testing and closure.

Community
Advanced
gquthiergquthier
14

systematic-debugging

Identifies root causes of bugs through a four-phase diagnostic process.

Community
Advanced