systematic-debugging

Enforce root-cause investigation before applying fixes in debugging workflows.

Updated Jan 16, 2026

Search Tags:#debugging #troubleshooting #quality-assurance #phases #software-engineering #root-cause-analysis #systematic-debugging

Ready to run

npx skills add https://github.com/Xinm123/MyRecall --skill systematic-debugging-xinm123

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/Xinm123/MyRecall/tree/main/openrecall/.trae/skills/systematic-debugging
Command: npx skills add https://github.com/Xinm123/MyRecall --skill systematic-debugging-xinm123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic Debugging prevents guesswork by requiring root-cause investigation before any fixes, reducing wasted time and avoiding new bugs.

Core Features & Use Cases

Phase-driven workflow: Root-cause investigation, pattern analysis, hypothesis testing, and controlled implementation.
Evidence-based debugging: Collect data across components to locate the real source of issues.
Practical guidance: Applies to test failures, production bugs, performance issues, and build/integration problems.

Quick Start

Phase 1: Read error messages carefully, reproduce the issue reliably, gather evidence across components.
Phase 2: Analyze patterns by finding working examples and noting differences.
Phase 3: Form a hypothesis and test minimally.
Phase 4: Implement the root-cause fix and verify results.

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 how does it help fix production bugs?▼

Systematic debugging is a root-cause investigation method that enforces evidence gathering and pattern analysis before applying fixes to production bugs, reducing guesswork and preventing new errors.

How do I troubleshoot test failures using a root-cause analysis approach?▼

Troubleshoot test failures by following a four-phase workflow: gather evidence across components, analyze patterns from working examples, form and test a minimal hypothesis, then implement and verify the fix.

What is the best way to debug software engineering issues without guesswork?▼

The best way to debug without guesswork is using an evidence-based approach that requires identifying the actual source of issues through hypothesis testing before any controlled implementation of a solution.

Can I apply systematic debugging to performance problems and build failures?▼

Yes, you can apply systematic debugging to performance problems and build failures. The root-cause investigation workflow adapts to various software issues including unexpected behavior and integration failures.

Why does fixing software bugs randomly often introduce new issues?▼

Fixing software bugs randomly introduces new issues because it skips root-cause investigation and pattern analysis, applying patches to symptoms rather than resolving the actual source of the problem.