skills.rest
MarbleSodas
MarbleSodasCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Diagnose technical failures through a four-phase investigation and validation workflow.

Updated Apr 9, 2026
Search Tags:#debugging#troubleshooting#root cause analysis#hypothesis testing#regression testing#test verification#data flow tracing
One-click install
npx skills add https://github.com/MarbleSodas/Mavis --skill systematic-debugging-marblesodas
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/MarbleSodas/Mavis/tree/main/skills/software-development/systematic-debugging
Command: npx skills add https://github.com/MarbleSodas/Mavis --skill systematic-debugging-marblesodas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents wasted time and repeated failures by forcing a disciplined root-cause investigation before proposing fixes, so you resolve the underlying cause rather than patching symptoms.

Core Features & Use Cases

  • Four-phase debugging workflow: investigation, pattern analysis, hypothesis testing, then root-cause implementation with verification.
  • Evidence-first troubleshooting: read and interpret errors, reproduce reliably, review recent changes, gather instrumentation, and trace data flow upstream.
  • Regression protection: create a failing test case first and run targeted then full test suites to confirm the fix and avoid regressions.
  • Failure guardrails: after 3+ unsuccessful fix attempts, stop and reassess architecture instead of continuing symptom thrashing.

Quick Start

Follow Phase 1 by reading the full error message, reproducing the issue consistently, and tracing the data flow upstream to identify the root cause before writing any fix.

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 root cause before changing code?▼

Root-cause debugging replaces guess-and-fix loops with a structured four-phase investigation workflow to identify and resolve the underlying cause rather than patching symptoms.

How do I debug a production bug using a structured workflow?▼

Debug a production bug by gathering evidence like logs and data flow traces, analyzing patterns, testing a single hypothesis, then implementing the root-cause fix validated by regression tests.

How do I troubleshoot multi-component system failures without guessing?▼

Troubleshoot multi-component failures by tracing data flow upstream, reproducing the issue consistently, reviewing recent changes, and testing minimal single-hypothesis fixes before implementation.

Can I use this debugging workflow for build and integration failures?▼

Yes, this troubleshooting workflow applies to build and integration failures by requiring evidence gathering, hypothesis testing, and root-cause implementation validated by regression tests.

What should I do when my fix attempts keep failing during debugging?▼

When experiencing three or more unsuccessful fix attempts, stop symptom thrashing and reassess the architecture before continuing the root-cause debugging workflow.

How do I prevent regressions when fixing an unexpected behavior issue?▼

Prevent regressions by creating a failing test case first, then running targeted and full test suites to confirm the root-cause fix resolves the unexpected behavior issue.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

Diagnose bugs by tracing evidence and generating a BR issue template.

Community
Advanced
robkamrobkam
12

bugfix-red-green-proof

Enforce a red-green-proof loop starting with a failing regression test.

Community
Advanced
fratilanicofratilanico
7

systematic-debugging

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

Community
Advanced
Likas07Likas07

systematic-debugging

Guide a 4-phase root cause investigation process for technical issues.

Community
Advanced