systematic-debugging

Identify root causes of bugs through a four-phase debugging workflow.

Updated Feb 5, 2026

Search Tags:#debugging #troubleshooting #process #phases #software-engineering #root-cause-analysis

Ready to run

npx skills add https://github.com/Khoiwall/be_vidify --skill systematic-debugging-khoiwall

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/Khoiwall/be_vidify/tree/main/.opencode/skill/systematic-debugging
Command: npx skills add https://github.com/Khoiwall/be_vidify --skill systematic-debugging-khoiwall

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Random fixes waste time and create new issues. Systematic debugging ensures you identify the true root cause of bugs, test failures, or unexpected behavior before proposing or applying any fixes.

Core Features & Use Cases

Phase-driven approach: Four mandatory phases (root-cause investigation, pattern analysis, hypothesis testing, implementation) to structure problem solving.
Evidence-first workflow: Emphasizes error interpretation, reproducibility, and data collection across system boundaries.
Skill integration: Leverages related capabilities such as root-cause-tracing and test-driven development to improve reliability and repeatability.

Quick Start

Begin with Phase 1: read error messages, reproduce the issue, review recent changes, and collect evidence before moving to Phase 2.

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 software troubleshooting?▼

Systematic debugging is a structured troubleshooting process that identifies the root cause of bugs before applying fixes. You need it when random fixes waste time, create new issues, or fail to resolve unexpected behavior in development or production environments.

How do I start debugging a bug using a phase-driven approach?▼

Start debugging by reading error messages, reproducing the issue, reviewing recent changes, and collecting evidence. This root-cause investigation phase ensures you gather data across system boundaries before moving to pattern analysis, hypothesis testing, and implementation.

What's the best way to find the root cause of a failure instead of applying random fixes?▼

The best way to find a root cause is applying a four-phase framework: root-cause investigation, pattern analysis, hypothesis testing, and implementation. This evidence-first workflow enforces pattern recognition and testable hypotheses to ensure thorough understanding before changes.

Can I use systematic debugging for production environments and test failures?▼

Yes, systematic debugging applies across both development and production environments. It guides troubleshooting for test failures and unexpected behavior by emphasizing error interpretation, reproducibility, and data collection across system boundaries.

How does systematic debugging work with root-cause tracing and test-driven development?▼

Systematic debugging integrates with root-cause-tracing and test-driven development skills to improve reliability and repeatability. It leverages these related capabilities during the hypothesis testing and implementation phases to ensure validated fixes.

Why does my debugging process keep introducing new issues when fixing bugs?▼

Your debugging process likely introduces new issues because fixes are applied before identifying the true root cause. Systematic debugging enforces evidence gathering, pattern recognition, and testable hypotheses to ensure thorough understanding before any changes are implemented.