skills.rest
yimwoo
yimwooCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Apply a four-phase debugging workflow to reproduce, understand, hypothesize, and verify fixes.

25|2|Updated Mar 5, 2026
Search Tags:#debugging#verification#quality-assurance#root-cause#reproduction#hypotheses#software-debugging
One-click install
npx skills add https://github.com/yimwoo/hotl-plugin --skill systematic-debugging-yimwoo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/yimwoo/hotl-plugin/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/yimwoo/hotl-plugin --skill systematic-debugging-yimwoo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging provides a repeatable, evidence-based approach to finding root causes and preventing regressions when bugs, test failures, or unexpected behavior occur.

Core Features & Use Cases

  • Four-phase methodology: Reproduce, Understand, Hypothesize, and Fix and Verify, with explicit guardrails.
  • Clear expectations for reproducible steps, hypothesis-driven testing, and verification before completion.
  • Suitable for teams seeking consistency in debugging workflows and quality engineering.

Quick Start

Apply the four-phase debugging workflow to a failing bug report to reproduce, understand, hypothesize, 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 a systematic debugging workflow for resolving software bugs?▼

A systematic debugging workflow provides a repeatable, evidence-based approach to finding root causes and preventing regressions. It applies a structured methodology to resolve bugs, test failures, or unexpected behavior across projects.

How do I find the root cause of a test failure using hypothesis-driven debugging?▼

To find the root cause of a test failure, you apply a four-phase process: Reproduce the issue, Understand the system, Hypothesize potential causes, and Fix and Verify. This ensures fixes are validated before completion.

Can I use this structured debugging methodology for any unexpected software behavior?▼

Yes, this structured debugging methodology applies to any bug, test failure, or unexpected behavior across different projects. It enforces consistent reproduction, hypothesis testing, and verification steps regardless of the software context.

What are the steps to reproduce and verify a bug fix?▼

The steps to reproduce and verify a bug fix follow a four-phase process: Reproduce the failure, Understand the underlying mechanism, Hypothesize the root cause, and Fix and Verify. A verification guardrail prevents completion before confirmation.

Why should my team use a disciplined workflow for software debugging?▼

Teams should use a disciplined debugging workflow to achieve consistency in quality engineering. It enforces clear expectations for reproducible steps, evidence-based hypothesis testing, and verification before completion, which prevents future regressions.

Related Skills

Explore More Software Engineering Skills→
mediar-aimediar-ai
1.6k

Terminator Issue Reporter

Generate structured GitHub issues for Terminator failures with logs and reproduction steps.

Official
Advanced
balajivisbalajivis
2

investigate

Identify root causes of software defects before applying code fixes.

Community
Advanced
isymchychisymchych

root-cause-analysis

Identify the deepest controllable root cause of a failure with evidence.

Community
Advanced
Pixel-Process-UGPixel-Process-UG
1

systematic-debugging

Guide structured four-phase debugging to resolve software defects.

Official
Advanced