systematic-debugging

Investigate bugs and test failures through root-cause analysis before applying fixes.

Updated Aug 27, 2026

Search Tags:#testing #debugging #investigation #root cause #troubleshooting #hypothesis #stack traces

Ready to run

npx skills add https://github.com/diegocondo10/sinai-intranet-backend --skill systematic-debugging-diegocondo10

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/diegocondo10/sinai-intranet-backend/tree/main/.agents/skills/systematic-debugging
Command: npx skills add https://github.com/diegocondo10/sinai-intranet-backend --skill systematic-debugging-diegocondo10

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents wasted time, brittle patches, and repeated failures by enforcing root-cause investigation before any fix is proposed.

Core Features & Use Cases

Root-Cause First Workflow: Guides you through careful evidence gathering, reproduction, recent-change review, and data-flow tracing before changing code.
Pattern and Hypothesis Testing: Helps compare against working examples, form a single hypothesis, and test minimally to confirm the real source of failure.
Production and Test Debugging: Useful for flaky tests, build failures, performance problems, integration issues, and multi-component incidents where the symptom is not the source.

Quick Start

Use the systematic-debugging skill to investigate the issue from symptoms to root cause before proposing or applying any fix.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

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

To find the root cause before fixing a bug, follow a systematic debugging workflow that enforces stepwise evidence gathering, reproduction, recent-change review, and data-flow tracing to pinpoint the actual source of failure rather than just treating the symptom.

What is the best way to troubleshoot flaky tests and build failures?▼

The best way to troubleshoot flaky tests and build failures is to compare against working examples, form a single hypothesis, and test minimally to confirm the real source of the unexpected behavior across logs, code, and environment state.

Why does fixing a symptom instead of the root cause lead to repeated failures?▼

Fixing a symptom instead of the root cause leads to repeated failures because the underlying fault remains in the code, causing wasted time and brittle patches that fail again when the same data-flow or environmental condition triggers the issue.

How do I debug production incidents and performance regressions across multiple components?▼

To debug production incidents and performance regressions across multiple components, trace the failure across logs, code, and environment state, then verify the root cause by creating a failing test before proposing any remediation.

Can I use systematic debugging for multi-component failures where the symptom is not the source?▼

Yes, systematic debugging is specifically designed for multi-component failures where the symptom is not the source, requiring pattern comparison and single-hypothesis testing to trace data-flow and isolate the true fault.