systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: tusosos

Identify and resolve software bug root causes through a four-phase evidence-driven process.

Updated Apr 3, 2026

Search Tags:#testing #debugging #systematic #tracing #root-cause #error-analysis

Ready to run

npx skills add https://github.com/tusosos/manus-knowledge-base --skill systematic-debugging-tusosos

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/tusosos/manus-knowledge-base/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/tusosos/manus-knowledge-base --skill systematic-debugging-tusosos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Random fixes waste time and create new bugs. This skill enforces a root-cause-first approach to debugging, reducing guesswork and rework.

Core Features & Use Cases

Phase-driven workflow: root-cause investigation, pattern analysis, hypothesis testing, and implementation to ensure fixes address the actual issue.
Evidence-based debugging: collect data at each component boundary and reproduce reliably before proposing changes.
Defensive validation: trace data flow, use reference techniques, and validate fixes with controlled tests.

Quick Start

Follow Phase 1 to identify and reproduce the root cause before attempting any fix.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

What is systematic debugging and when do I need it for root cause analysis?▼

Systematic debugging is an evidence-driven approach that enforces root cause analysis before applying fixes. You need it when random fixes waste time or create new bugs, ensuring you resolve actual issues across test failures, production bugs, and performance problems.

How do I find the root cause of a bug using a systematic debugging approach?▼

To find a root cause, follow a four-phase workflow: investigate root causes, analyze patterns, test hypotheses, and implement fixes. You must reproduce the issue reliably and collect data at component boundaries before proposing any changes.

What is the best way to debug production bugs and performance problems without introducing new errors?▼

The best way to debug production bugs and performance problems is using defensive validation. Trace data flow, apply reference techniques, and validate fixes with controlled tests to ensure changes do not introduce new errors.

How do I trace data flow across software systems to resolve integration issues?▼

Trace data flow by collecting evidence at each component boundary across your software systems. This reproduces integration issues reliably and supports pattern comparison to identify the actual root cause before implementation.

Does systematic debugging work for test failures and integration issues across different software systems?▼

Yes, systematic debugging works for test failures, production bugs, performance problems, and integration issues across software systems. It enforces strict reproducibility and data-traceability requirements to validate fixes across diverse environments.

Why should I not apply immediate fixes without reproducing the error first?▼

Applying immediate fixes without reproducing the error first leads to guesswork and rework. Enforcing strict reproducibility and data-traceability ensures your hypothesis is validated against actual evidence before implementation, preventing new bugs.