skills.rest
oabdelmaksoud
oabdelmaksoudCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Guides users through root-cause investigation to implementation for software bugs.

4|Updated Feb 26, 2026
Search Tags:#testing#debugging#troubleshooting#quality-assurance#root-cause#software-engineering#phase-based
One-click install
npx skills add https://github.com/oabdelmaksoud/Openclaw-skills-Compilations --skill systematic-debugging-oabdelmaksoud
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/oabdelmaksoud/Openclaw-skills-Compilations/tree/main/systematic-debugging
Command: npx skills add https://github.com/oabdelmaksoud/Openclaw-skills-Compilations --skill systematic-debugging-oabdelmaksoud

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Random fixes waste time and create new bugs. Systematic Debugging ensures root-cause investigation precedes any fix, reducing rework and improving reliability.

Core Features & Use Cases

  • Phase-based approach from root-cause investigation to implementation, providing a repeatable debugging workflow.
  • Rich guidance on data-flow tracing, evidence collection, hypothesis testing, and safe fixes for multi-component systems.
  • Ideal for test failures, production bugs, flaky behavior, and complex integrations where symptoms conceal root causes.

Quick Start

Start with Phase 1: observe the symptom, reproduce it reliably, gather diagnostic evidence, and trace data flow before proposing 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 the root cause of flaky behavior in multi-component systems?▼

A systematic debugging workflow identifies root causes by tracing data flows and collecting diagnostic evidence before proposing fixes. It guides you from phase one investigation through phase four implementation to reduce rework.

How do I debug production bugs without creating new issues from random fixes?▼

Debug production bugs by observing symptoms, reproducing them reliably, and validating fixes through evidence collection. Systematic debugging ensures you test hypotheses and trace data flows before implementation to prevent new bugs.

Can I use a phase-based troubleshooting workflow for complex test failures?▼

Yes, phase-based troubleshooting is ideal for test failures. The workflow starts with phase one root-cause investigation to observe and reproduce symptoms, then progresses through implementation to resolve complex test failures.

When do I need systematic debugging for software engineering tasks?▼

You need systematic debugging when symptoms conceal root causes in multi-component systems. It is ideal for complex integrations, flaky behavior, and production bugs where random fixes waste time and create new issues.

Why does tracing data flow matter when troubleshooting software bugs?▼

Tracing data flow matters because it helps you collect diagnostic evidence and validate hypotheses across components. This systematic approach ensures you identify the actual root cause instead of applying random fixes that fail.

Related Skills

Explore More Software Engineering Skills→
I194I194
9

investigate

Guide root-cause debugging through four investigation phases before proposing fixes.

Community
Advanced
liujiarui0918liujiarui0918

root-cause-tracing

Trace call stacks and apply Five Whys to identify software bug root causes.

Community
Advanced
CodingCossackCodingCossack
19

systematic-debugging

Trace data flow to identify root causes of software bugs.

Community
Advanced
gztcodegztcode

systematic-debugging

Automate debugging with a four-phase root cause analysis approach.

Community
Advanced