skills.rest
Icebane84
Icebane84COMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Guide evidence-based debugging through reproduce, isolate, root-cause, and fix phases.

Updated Mar 24, 2026
Search Tags:#debugging#root cause analysis#evidence#incident response#regression testing#grep#git log
One-click install
npx skills add https://github.com/Icebane84/Synarche_Workshop --skill systematic-debugging-icebane84
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/Icebane84/Synarche_Workshop/tree/main/.agent/skills/qa/systematic-debugging
Command: npx skills add https://github.com/Icebane84/Synarche_Workshop --skill systematic-debugging-icebane84

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents random debugging by guiding you through a disciplined process that reproduces issues, isolates variables, identifies root causes, and verifies fixes with evidence.

Core Features & Use Cases

  • 4-Phase Debugging Method: Reproduce consistently, isolate the source, perform root-cause analysis, then fix and verify to ensure the issue is truly resolved.
  • Root Cause Analysis Framework: Uses structured methods like the 5 Whys to move from symptoms to underlying causes.
  • Evidence-Based Execution Mandate: Promotes an IPPD Shadow-Logging requirement to capture metacognitive “shadow logs” for disciplined operational runs.
  • Use Cases: Apply to complex bugs in software systems, regressions in existing functionality, and troubleshooting when prior fixes failed or changes were unclear.

Quick Start

Use systematic-debugging to resolve a complex production bug by following the 4 phases from a reliable reproduction to a verified root-cause fix.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is evidence-based debugging and how does it fix vague software failures?▼

Evidence-based debugging is a disciplined approach that resolves vague software failures by consistently reproducing the issue, isolating variables, and performing root-cause analysis before fixing and verifying. It prevents random trial-and-error troubleshooting.

How do I debug a complex regression when the recent code changes are unclear?▼

To debug a complex regression with unclear changes, use a structured root-cause analysis framework like the 5 Whys. This moves you past superficial symptoms to identify underlying causes, ensuring you verify the fix with concrete evidence.

Can I use systematic debugging for multi-factor troubleshooting across different environments?▼

Yes, systematic debugging is designed for multi-factor troubleshooting across different environments. It handles complex software incidents by isolating variables and identifying root causes when changes and symptoms are unclear or span multiple systems.

Why should I avoid random debugging during an incident response?▼

Avoid random debugging during incident response because guessing wastes time and introduces risk. A systematic approach requires a reproducible, isolated, and root-caused workflow, ensuring you verify the true fix rather than masking symptoms.

Related Skills

Explore More Software Engineering Skills→
fajjarnrfajjarnr

debugging-methodology

Guide systematic root cause debugging through four phases with hypothesis testing.

Community
Basic
Chang-Shih-YungChang-Shih-Yung

gstack-openclaw-investigate

Enforces a four-phase root cause workflow for web and backend system debugging.

Community
Advanced
duy-tungduy-tung

ck:journal

Analyze recent code changes to create structured technical journal entries.

Community
Intermediate
photonics-dhlphotonics-dhl

systematic-debugging

Enforce a four-phase root-cause investigation for software bugs.

Community
Advanced