skills.rest
hussain9491
hussain9491COMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Investigate root causes of software bugs through phased hypothesis testing.

Updated Jan 5, 2026
Search Tags:#debugging#systematic#traceability#phases#root-cause#bug-investigation
One-click install
npx skills add https://github.com/hussain9491/hackathone2_phase2_Q4 --skill systematic-debugging-hussain9491
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/hussain9491/hackathone2_phase2_Q4/tree/main/.claude/skills/systematic-debugging
Command: npx skills add https://github.com/hussain9491/hackathone2_phase2_Q4 --skill systematic-debugging-hussain9491

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Systematic methodology for debugging bugs, test failures, and unexpected behavior. Use when encountering any technical issue before proposing fixes. It covers root cause investigation, pattern analysis, hypothesis testing, and structured fix implementation. Use especially when under time pressure, when a quick fix seems obvious, or when you have already tried multiple fixes. Not for exploratory code reading.

Core Features & Use Cases

This skill enforces a disciplined debugging workflow that focuses on root-cause identification rather than symptom fixes. It emphasizes four phases (Phase 1: Root Cause Investigation, Phase 2: Pattern Analysis, Phase 3: Hypothesis and Testing, Phase 4: Implementation), along with defense-in-depth, traceability, and decision gates to prevent regressions. It also highlights red flags that signal when to stop and re-evaluate the approach.

Quick Start

Describe the issue, reproduce it, trace data flow, and apply Phases 1 through 4 to identify the root cause before implementing a fix.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is the best way to find the root cause of flaky tests and integration failures?▼

To debug unexpected software behavior, first describe and reproduce the issue, then trace data flow across components. Apply four phases: root cause investigation, pattern analysis, hypothesis testing, and documented verification before committing any code changes.

How do I stop applying quick fixes and systematically debug multi-component software issues?▼

Systematic debugging enforces a disciplined workflow using decision gates and traceability. Instead of applying quick fixes, it guides you through root cause investigation, pattern analysis, and hypothesis testing to ensure the actual issue is resolved.

When should I use a phase-based bug investigation methodology instead of exploratory code reading?▼

Use phase-based bug investigation when encountering technical issues like error traces or flaky tests under time pressure, especially after multiple failed fixes. It is not intended for exploratory code reading or understanding unfamiliar codebases.

How do I prevent regressions when implementing fixes for unexpected software behavior?▼

Prevent regressions during bug fixes by applying defense-in-depth and documented verification. The methodology requires passing through decision gates and confirming the root cause before implementing changes to avoid introducing new failures.

What are the red flags that I should stop and re-evaluate my debugging approach?▼

Red flags signaling you should re-evaluate your debugging approach include situations where a quick fix seems obvious or when you have already tried multiple fixes without success, indicating a need for structured root cause investigation.

Related Skills

Explore More Software Engineering Skills→
icartshicartsh
4

error-detective

Parse stack traces and guide error resolution with the TRACE framework.

Community
Advanced
Agentic-AssetsAgentic-Assets

debugging-wizard

Identify and isolate software root causes through structured reproduction and hypothesis testing.

Official
Advanced
hungtrandigitalhungtrandigital

debugging

Guide root-cause investigation through a four-phase systematic debugging workflow.

Community
Advanced
jamestorrevillasjamestorrevillas
3

code-reading

Guide engineers through structured code-reading strategies for unfamiliar codebases.

Community
Intermediate