systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: liu5540

Trace root causes of bugs through a four-phase evidence-driven workflow.

78|6|Updated May 19, 2026

Search Tags:#debugging #maintainability #quality-assurance #root-cause #test-driven-development #systems-thinking #issue-tracing

Ready to run

npx skills add https://github.com/liu5540/reasonix-skill-powers --skill systematic-debugging-liu5540

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/liu5540/reasonix-skill-powers/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/liu5540/reasonix-skill-powers --skill systematic-debugging-liu5540

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams consistently identify and trace the root cause of bugs, failures, or abnormal behavior before proposing fixes.

Core Features & Use Cases

Phase-driven debugging: root-cause investigation, pattern analysis, hypothesis validation, and implementation with enforced checkpoints.
Evidence-driven workflow: structured data collection, traceable diagnosis, and non-symptomatic fixes.
Use Case: during a flaky test run, you follow the four phases to isolate the root cause and prevent regression.

Quick Start

Follow the four-phase workflow to identify root causes before applying fixes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

How do I identify the root cause of a bug before implementing a fix?▼

To identify the root cause of a bug, you gather evidence and trace the diagnosis through a four-phase workflow: investigation, pattern analysis, hypothesis validation, and implementation, ensuring you fix the source rather than symptoms.

What is the best way to debug flaky tests without masking the real issue?▼

The best way to debug flaky tests is following an evidence-driven workflow that isolates the root cause through pattern analysis and hypothesis validation, preventing symptomatic fixes and future regressions.

Can I use this systematic debugging approach across different tech stacks?▼

Yes, you can use this systematic debugging approach across any tech stack and testing scenario, including production incidents and flaky tests, because it relies on structured data collection rather than stack-specific tools.

Why does my debugging process often result in recurring software failures?▼

Debugging often results in recurring failures when symptom fixes are applied; enforcing explicit checkpoints and evidence-driven root-cause tracing prevents treating symptoms as the actual source of the system's abnormal behavior.

How to validate debugging hypotheses during a complex production incident?▼

To validate debugging hypotheses during a production incident, you apply the hypothesis validation phase of the workflow, using structured data collection and traceable diagnosis to confirm the root cause before applying fixes.