systematic-debugging

Identify root causes of bugs and test failures before proposing fixes.

Updated Aug 27, 2026

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

Ready to run

npx skills add https://github.com/victorqnguyen/victors-architecture --skill systematic-debugging-victorqnguyen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/victorqnguyen/victors-architecture/tree/main/packages/core/skills/systematic-debugging
Command: npx skills add https://github.com/victorqnguyen/victors-architecture --skill systematic-debugging-victorqnguyen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic Debugging helps engineers identify root causes before patching code, reducing wasted time and rework.

Core Features & Use Cases

Structured Phase Workflow: guides Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation with guardrails.
Evidence-driven Debugging: mandates reproducible steps, data-gathering, and validation before fixes.
Reusable Techniques Library: references to root-cause-tracing, defense-in-depth, and condition-based waiting for deeper diagnostics.

Quick Start

Reproduce the issue, then follow Phase 1 through Phase 4 to identify the root cause and verify the 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 should I use it for troubleshooting?▼

Systematic debugging is a structured approach to identify the root cause of bugs, test failures, or unexpected behavior before proposing fixes. Use it for any software troubleshooting, including production issues, build failures, and integration problems.

How do I find the root cause of a bug before writing a fix?▼

To find the root cause of a bug, follow a structured phase workflow covering Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation. This process mandates gathering evidence and validating hypotheses before applying code fixes.

Does systematic debugging work for production issues and build failures?▼

Yes, systematic debugging applies to production issues, build failures, and integration problems. It guides you through evidence-driven troubleshooting and root-cause tracing to ensure you resolve the actual software engineering defect.

What is the best way to troubleshoot unexpected software behavior without causing rework?▼

The best way to troubleshoot unexpected behavior without rework is using an evidence-driven debugging process. Reproduce the issue, gather data, and verify the fix through a four-phase workflow to ensure successful validation before finishing.

How do I test debugging hypotheses systematically during root cause analysis?▼

You test debugging hypotheses systematically by applying a structured phase workflow that requires completing evidence gathering and pattern analysis first. This method uses condition-based waiting and validation to confirm the root cause before implementation.

Why does my debugging process fail to prevent recurring software issues?▼

Your debugging process likely fails because fixes are applied before identifying the root cause. Systematic debugging prevents recurring issues by mandating reproducible steps, evidence gathering, and root-cause investigation before modifying code.