systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: YangYuS8

Identify and isolate root causes of bugs before proposing fixes.

Updated Apr 15, 2026

Search Tags:#workflow #testing #debugging #systematic #phases #root-cause

Ready to run

npx skills add https://github.com/YangYuS8/dev-2026-grading --skill systematic-debugging-yangyus8

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/YangYuS8/dev-2026-grading/tree/main/.opencode/skills/systematic-debugging
Command: npx skills add https://github.com/YangYuS8/dev-2026-grading --skill systematic-debugging-yangyus8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging provides a disciplined approach to identify and isolate root causes of bugs, test failures, or anomalous behavior before proposing fixes.

Core Features & Use Cases

Phase-driven workflow (Investigation → Pattern Analysis → Hypothesis → Implementation) that resists quick, symptom-focused patches.
Explicit root-cause tracing and anti-pattern defenses to prevent shortcuts under pressure.
Guidance for multi-layer defenses and documentation of diagnostic points to ensure reproducibility across teams.

Quick Start

Follow Phase 1 before proposing any fix to ensure root cause is identified.

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 instead of just patching symptoms?▼

Root-cause debugging enforces a four-phase workflow—investigation, pattern analysis, hypothesis, and implementation—to isolate why bugs occur before applying fixes, resisting quick symptom-focused patches.

What is the best way to debug test failures systematically?▼

Systematic debugging identifies and isolates root causes of test failures by tracing patterns and forming hypotheses during analysis phases, ensuring you address the underlying anomaly rather than superficial errors.

How do I structure a debugging workflow to avoid taking shortcuts under pressure?▼

A phase-driven workflow with explicit anti-pattern defenses prevents shortcuts by mandating root-cause tracing and multi-layer guards, guiding you sequentially through investigation, pattern analysis, hypothesis, and implementation.

Can I use systematic debugging for anomalous behavior without clear error messages?▼

Yes, the investigation and pattern analysis phases are designed to identify and isolate root causes of anomalous behavior by tracing systemic patterns before proposing any fixes.

Why should I complete an investigation phase before proposing a bug fix?▼

Completing investigation first ensures the root cause is fully identified and isolated, preventing premature fixes that address only symptoms and making diagnostic points reproducible across teams.

What are the limitations of systematic debugging for urgent production incidents?▼

The mandatory four-phase workflow resists quick patches, meaning it prioritizes thorough root-cause isolation over immediate symptom mitigation, which may not suit incidents requiring instant mitigation.