Verified:GitHub

systematic-debugging

Guide root-cause debugging through a four-phase investigation before implementing fixes.

Updated May 5, 2026

Search Tags:#debugging #troubleshooting #pytest #test-driven development #systematic investigation #root-cause analysis #data flow tracing

Ready to run

npx skills add https://github.com/Z43L/zeus-agent --skill systematic-debugging-z43l

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/Z43L/zeus-agent/tree/main/skills/software-development/systematic-debugging
Command: npx skills add https://github.com/Z43L/zeus-agent --skill systematic-debugging-z43l

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging prevents wasted time and recurring bugs by forcing disciplined root-cause investigation before any code change.

Core Features & Use Cases

Four-phase workflow: Investigate, analyze patterns, form and test hypotheses, then implement and verify.
Evidence-first approach: Reads errors carefully, reproduces issues consistently, traces data flow, and inspects recent changes.
Test-driven repair: Creates a failing regression test before fixing to prevent recurrence.
Works for technical failures: Applies to test failures, production bugs, performance regressions, build/integration issues.

Quick Start

Ask the agent to debug a failing test by following the four phases and producing a root-cause explanation before proposing a 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?▼

Systematic debugging is a disciplined, four-phase root-cause investigation process used before fixing software failures. You should use it for failing tests, production bugs, performance regressions, and build or integration errors to prevent wasted time and recurring issues.

How do I find the root cause of a failing test without guessing?▼

To find the root cause of a failing test, follow a four-phase workflow: investigate by reading full error messages, reproduce the issue consistently with terminal commands, analyze data flow patterns, form minimal hypothesis tests, and implement a fix only after creating a failing regression test.

How to troubleshoot production bugs using a test-driven repair approach?▼

Troubleshoot production bugs by enforcing an evidence-first investigation that traces data flow and inspects recent changes. The test-driven repair approach requires creating a failing regression test that reproduces the bug before implementing any code changes to verify the fix and prevent recurrence.

Can I use this systematic investigation method for build and integration errors?▼

Yes, this systematic investigation method applies to build and integration errors. It enforces reading full error messages and tracing dependencies to understand the failure pattern, ensuring you validate the root cause with minimal hypothesis tests before applying any fixes.

What's the best way to stop recurring software bugs after deployment?▼

The best way to stop recurring software bugs is to use a test-driven repair workflow. This approach mandates creating a failing regression test that captures the exact failure before fixing the code, ensuring the specific issue is permanently resolved and verified.