skills.rest
Asmayaseen
AsmayaseenCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Identify root causes of software bugs through a four-phase evidence-based debugging process.

2|Updated Dec 24, 2025
Search Tags:#debugging#root cause#problem-solving#tracing#software#phase-based
One-click install
npx skills add https://github.com/Asmayaseen/hackathon-2 --skill systematic-debugging-asmayaseen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/Asmayaseen/hackathon-2/tree/main/.claude/skills/systematic-debugging
Command: npx skills add https://github.com/Asmayaseen/hackathon-2 --skill systematic-debugging-asmayaseen

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Systematic debugging provides a disciplined approach to identify the root cause of bugs and failures, preventing symptom-based fixes and reducing regression risk.

Core Features & Use Cases

  • Phase-driven investigation: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation to guide every debugging effort.
  • Evidence-first workflow: collect data, reproduce reliably, trace data flow, and validate fixes against root cause.
  • Defensive practices: enforce four-phase process, use defense-in-depth instrumentation, and stop fixes until the root cause is established.

Quick Start

Follow the four-phase process on a failing issue: read errors, reproduce, trace, hypothesize, test, and implement only after confirming root cause.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is systematic debugging and how does it find root causes?▼

Systematic debugging is a disciplined approach that identifies root causes of bugs through evidence-based validation. It prevents symptom-based fixes by enforcing a four-phase process: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation.

How do I debug flaky tests and integration issues across multi-component applications?▼

Debug flaky tests and integration issues by following the four-phase workflow: read errors, reproduce reliably, trace data flow, and hypothesize. You only implement fixes after confirming the root cause through evidence-based validation.

What's the best way to trace data flow during a time-pressed software failure?▼

The best way to trace data flow during time-pressed fixes is using evidence-first investigation. Collect data, reproduce the failure reliably, and apply defense-in-depth instrumentation to establish root causes before making any code changes.

When should I stop a symptom-based fix and investigate the root cause instead?▼

You should stop a symptom-based fix immediately and investigate the root cause when you cannot reliably reproduce the bug or validate the fix against established evidence. The process enforces stopping all fixes until the root cause is confirmed.

Can I use this debugging process for any codebase or does it require specific dependencies?▼

You can use this debugging process across any codebase and multi-component application without specific dependencies. It applies to time-pressed fixes, flaky tests, and integration issues by enforcing a phase-driven investigation workflow.

Related Skills

Explore More Software Engineering Skills→
enoch-robinsonenoch-robinson

debug-helper

Guide users through structured debugging to reproduce issues and identify root causes.

Community
Basic
simonwjacksonsimonwjackson

se-debug

Trace causal chains from trigger to symptom to confirm root causes.

Community
Advanced
fratilanicofratilanico
7

systematic-debugging

Trace bugs to root causes through call chains and data flow.

Community
Advanced
frankxaifrankxai
6

intelligence/pattern-recognition

Identify recurring patterns and anti-patterns across code, architecture, and content.

Community
Intermediate