systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: chikage0o0

Enforce a four-phase root-cause debugging process for test failures and errors.

34|6|Updated Jan 19, 2026

Search Tags:#testing #debugging #systematic #hypothesis #root-cause #error-investigation

Ready to run

npx skills add https://github.com/Chikage0o0/opencode --skill systematic-debugging-chikage0o0

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It stops developers from chasing symptom‑only patches by enforcing a disciplined, root‑cause‑first debugging workflow for any error, test failure, or unexpected behavior.

Core Features & Use Cases

Four‑phase process: Root cause investigation, pattern analysis, hypothesis testing, and implementation with validation.
Anti‑pattern safeguards: Explicit warnings against shortcut fixes, multiple‑change attempts, and skipping investigation.
Applicable scenarios: Production outages, flaky tests, performance regressions, or any code breakage where a reliable fix is needed.
Guidance integration: Provides checklists, red‑flag alerts, and references to complementary skills such as test‑driven development and defense‑in‑depth.

Quick Start

Invoke the systematic debugging skill to analyze a failing test or error by requesting a step‑by‑step root‑cause investigation.

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 failing test instead of just patching the symptom?▼

To find the root cause of a failing test, use a systematic debugging process that enforces reproducible investigation steps, pattern analysis, and hypothesis testing before applying any code fixes. This prevents symptom-only patches.

What is the best way to debug production errors and prevent them from recurring?▼

The best way to debug production errors is enforcing a root-cause-first workflow with hypothesis testing and validation. This systematic investigation ensures you fix the underlying issue rather than applying temporary symptom patches.

How do I investigate flaky tests systematically without making random code changes?▼

Investigate flaky tests systematically by following a four-phase process: root cause investigation, pattern analysis, hypothesis testing, and implementation with validation, explicitly avoiding multiple-change attempts or shortcut fixes.

Can I use systematic debugging for performance regressions and unexpected code behavior?▼

Yes, you can use systematic debugging for performance regressions and unexpected behavior. It mandates reproducible investigation steps and hypothesis testing to guide error investigation and ensure reliable fixes across any code breakage scenario.

Why do my bug fixes keep causing new errors in production?▼

Bug fixes cause new errors when developers skip investigation and apply symptom patches. Systematic debugging prevents this by enforcing a disciplined root-cause-first workflow with anti-pattern safeguards against shortcut fixes and multiple-change attempts.

When should I avoid systematic debugging for error investigation?▼

You should not avoid systematic debugging for error investigation, but note it mandates a four-phase process. If you need an immediate shortcut fix without hypothesis testing or validation, this root-cause investigation workflow will intentionally block rapid patches.