skills.rest
tim-hub
tim-hubCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Apply a four-phase debugging framework to diagnose and fix software issues.

Updated Feb 17, 2026
Search Tags:#quality-assurance#software-engineering#pattern-analysis#root-cause-investigation#hypothesis-testing#systematic-debugging#data-tracing
One-click install
npx skills add https://github.com/tim-hub/role-based-skills --skill systematic-debugging-tim-hub
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/tim-hub/role-based-skills/tree/main/systematic-debugging
Command: npx skills add https://github.com/tim-hub/role-based-skills --skill systematic-debugging-tim-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions

Core Features & Use Cases

  • Provides a disciplined, phase-based approach to identify root causes, analyze patterns, test hypotheses, and implement fixes only after understanding the issue.
  • Reduces waste from quick patches by enforcing evidence collection, reproducible steps, and cross-component tracing.
  • Applicable to test failures, production bugs, unexpected behavior, performance issues, and integration problems to improve first-time fix rate.

Quick Start

Begin with Phase 1: Root Cause Investigation by reading errors, reproducing the issue, and gathering evidence, then progress through Phases 2–4 before implementing a fix.

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 the symptoms?▼

To find a bug's root cause, apply a systematic debugging framework that separates root cause investigation, pattern analysis, and hypothesis testing from the actual implementation, ensuring you fully understand the issue before attempting any fixes.

What is the best way to debug test failures and unexpected software behavior?▼

The best way to debug test failures and unexpected behavior is to follow a four-phase framework: gather evidence, reproduce the issue, trace data flow across components, and test controlled hypotheses before implementing a validated fix.

How do I trace data flow across components to solve integration problems?▼

Tracing data flow to solve integration problems requires reading errors, reproducing the issue, and gathering evidence to analyze patterns, which guides controlled hypothesis testing before you implement and validate the fix.

Can I use systematic debugging for performance issues and production bugs?▼

Yes, systematic debugging is applicable for performance issues, production bugs, test failures, unexpected behavior, and integration problems, enforcing evidence collection and reproducible steps to improve the first-time fix rate.

Why does applying quick patches often fail to fix unexpected behavior permanently?▼

Quick patches fail because they bypass root cause investigation and pattern analysis, leading to incomplete fixes; systematic debugging enforces evidence gathering and hypothesis testing to ensure the behavior is fully understood first.

Related Skills

Explore More Software Engineering Skills→
allexcdallexcd

autonomous-bug-fixing

Diagnose, reproduce, and fix code defects from bug reports or error logs.

Community
Advanced
robkamrobkam
12

bugfix-red-green-proof

Enforce a red-green-proof loop starting with a failing regression test.

Community
Advanced
d-o-hubd-o-hub
11

rust-code-quality

Review Rust code quality across eight dimensions including async patterns and error handling.

Community
Advanced
aleph23aleph23

When Stuck - Problem-Solving Dispatch

Map stuck symptoms to structured problem-solving techniques for debugging and troubleshooting.

Community
Intermediate