skills.rest
mway
mwayCOMMUNITY
Explore all skills by this author →
Website𝕏@mwayGitHub

systematic-debugging

Identify root causes of bugs and test failures through a four-phase debugging workflow.

4|Updated Sep 6, 2013
Search Tags:#debugging#troubleshooting#problem-solving#root-cause#software-engineering#root-cause-tracing
One-click install
npx skills add https://github.com/mway/dotfiles --skill systematic-debugging-mway
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/mway/dotfiles/tree/main/home/dot_codex/skills/systematic-debugging
Command: npx skills add https://github.com/mway/dotfiles --skill systematic-debugging-mway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging helps you identify the root cause of bugs, failing tests, and unexpected behavior before implementing fixes.

Core Features & Use Cases

  • Phase-based approach: root-cause investigation, pattern analysis, hypothesis testing, and guarded implementation
  • Ensures evidence-based reasoning and traceability across boundaries
  • Useful for performance issues and complex failure modes in software systems

Quick Start

Describe a failing scenario, reproduce it consistently, and apply the four-phase root-cause workflow to identify and fix the issue.

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 bug instead of just patching the symptom?▼

Root-cause debugging applies a four-phase workflow—investigation, pattern analysis, hypothesis testing, and guarded implementation—to trace data flow and verify fixes. This systematic approach ensures evidence-based reasoning to identify the true source of failures.

What is the best way to systematically troubleshoot complex software failures?▼

Systematic troubleshooting uses a phase-based approach to reproduce failures consistently and collect evidence. By tracing data flow and validating hypotheses during each phase, it ensures verifiable fixes for complex failure modes in software systems.

How do I trace data flow to reproduce a failing test scenario?▼

Tracing data flow to reproduce a failing test requires describing the failing scenario and applying the root-cause investigation phase. This process collects evidence across boundaries to ensure consistent reproduction before hypothesis testing begins.

Does systematic debugging work for performance issues across different codebases?▼

Systematic debugging works across development environments and codebases to address performance issues. It applies evidence-based reasoning and traceability to handle complex failure modes, ensuring fixes are verifiable regardless of the system.

When should I use hypothesis testing during software troubleshooting?▼

Hypothesis testing is used during the third phase of software troubleshooting after collecting evidence and analyzing patterns. It validates potential root causes before implementation, ensuring that the applied fix directly addresses the verified source of the unexpected behavior.

Related Skills

Explore More Software Engineering Skills→
Milky2018Milky2018
29

fix-bug

Reproduce Moon-based bugs, diagnose root causes, create regression tests, and submit PRs.

Community
Intermediate
pcaokhaipcaokhai

investigate

Trace software bugs to root causes through a structured multi-phase investigation workflow.

Community
Advanced
fratilanicofratilanico
7

systematic-debugging

Trace bugs to root causes through call chains and data flow.

Community
Advanced
valtterimelkkovaltterimelkko
1

systematic-debugging

Investigate root causes through a four-phase debugging framework before modifying code.

Community
Advanced