skills.rest
jacketlong23
jacketlong23COMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Guide a four-phase debugging process for root cause analysis.

Updated Aug 23, 2026
Search Tags:#debugging#root cause#troubleshooting#error handling#bug fixing#systematic process
One-click install
npx skills add https://github.com/jacketlong23/skills --skill systematic-debugging-jacketlong23
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/jacketlong23/skills/tree/main/systematic-debugging
Command: npx skills add https://github.com/jacketlong23/skills --skill systematic-debugging-jacketlong23

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill prevents wasted time and new bugs caused by quick fixes or symptom-based patching, ensuring that the true root cause of any technical issue is identified and resolved.

Core Features & Use Cases

  • Structured Debugging Process: Guides users through four distinct phases: Investigation, Pattern Analysis, Hypothesis, and Implementation.
  • Root Cause Mandate: Emphasizes finding the underlying issue before applying any solution.
  • Pressure Resistance: Includes specific language and structural defenses to prevent shortcuts under time pressure or urgency.
  • Use Case: When a critical API is failing in production, instead of guessing a quick fix, use this Skill to systematically trace the error, identify the exact point of failure, and implement a robust solution, saving hours of debugging and preventing future occurrences.

Quick Start

Use the systematic_debugging skill to investigate any bug or unexpected behavior you encounter.

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

To find the root cause of a bug, follow a structured debugging process of investigation, pattern analysis, hypothesis testing, and implementation. This ensures you trace the exact point of failure using evidence rather than applying quick symptom patches.

What is the best way to debug a critical API failure in a complex system?▼

The best way to debug a critical API failure is systematically tracing data flow and gathering evidence. A structured debugging approach mandates identifying the exact point of failure before implementing a robust solution to prevent future occurrences.

How do I stop taking debugging shortcuts when fixing production issues under time pressure?▼

To resist time pressure during production troubleshooting, use a debugging process with specific structural defenses against rationalizations. These rules mandate evidence gathering and hypothesis testing before applying any code changes.

What are the four phases of a systematic debugging process?▼

The four phases of systematic debugging are Investigation, Pattern Analysis, Hypothesis, and Implementation. This structured progression ensures thorough root cause analysis and prevents wasted time caused by guessing or symptom-based patching.

When should I use a systematic troubleshooting process for bug fixing?▼

You should use systematic troubleshooting for bug fixing whenever you encounter unexpected behavior in complex systems. It prevents new bugs caused by quick fixes by mandating data flow tracing and evidence gathering to resolve the true root cause.

Related Skills

Explore More Software Engineering Skills→
Ilenburg1993Ilenburg1993
3

reactive-bug-audit

Analyze stack traces and logs to identify root causes and apply minimal patches.

Community
Intermediate
pcaokhaipcaokhai

investigate

Trace software bugs to root causes through a structured multi-phase investigation workflow.

Community
Advanced
htlin222htlin222
77

error-detective

Search and analyze log files and codebases for error patterns and stack traces.

Community
Intermediate
bobmatnycbobmatnyc
146

systematic-debugging

Enforce a four-phase root-cause investigation framework for software debugging.

Community
Basic