skills.rest
ehartye
ehartyeCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Guide a four-phase process to identify and resolve software bug root causes.

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

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 by ensuring that the root cause of any issue is identified and addressed before any fixes are implemented. It combats the tendency to apply quick patches that only mask symptoms.

Core Features & Use Cases

  • Systematic Four-Phase Process: Guides users through Investigation, Pattern Analysis, Hypothesis, and Implementation.
  • Root Cause Mandate: Emphasizes finding the fundamental issue, not just treating symptoms.
  • Pressure Resistance: Includes specific language and structural defenses against rationalization under time pressure.
  • Use Case: When a critical API endpoint starts returning errors, instead of guessing at a fix, use this Skill to systematically trace the problem back to its origin, ensuring a permanent solution.

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
What is the best way to find the root cause of a software bug instead of just patching symptoms?▼

Systematic debugging enforces strict adherence to a four-phase process of investigation, pattern analysis, hypothesis testing, and implementation, preventing quick patches that only mask symptoms and cause recurring issues.

How do I stop myself from guessing fixes when troubleshooting an API endpoint returning unexpected errors?▼

Troubleshooting unexpected API errors requires a structured process that resists rationalization under time pressure by enforcing detailed evidence gathering and hypothesis testing before any implementation begins.

What steps should I follow for systematic error handling when my codebase has unexpected behavior?▼

Systematic error handling follows four phases: Investigation for evidence gathering, Pattern Analysis, Hypothesis generation, and Implementation, ensuring the fundamental issue is addressed before fixes are applied.

How do I debug a bug fix that keeps failing after multiple attempts?▼

When multiple bug fixes fail, systematic debugging supports architectural questioning and deep pattern analysis to re-evaluate the root cause, ensuring you move past incorrect assumptions to find the true origin.

When should I use a systematic debugging process instead of applying a quick patch?▼

A systematic debugging process is needed when a critical endpoint fails or unexpected behavior persists, preventing wasted time and new bugs by ensuring the root cause is identified and resolved before implementation.

Related Skills

Explore More Software Engineering Skills→
kynoptickynoptic
1

Debugging Runtime Errors

Analyze stack traces and error logs to identify root causes and propose fixes.

Community
Advanced
santanapolsantanapol

debugging-and-error-recovery

Diagnose failing tests, build errors, and runtime issues with structured triage workflows.

Community
Advanced
BubbleBufferBubbleBuffer
3

systematic-debugging

Enforce root-cause investigation before patching software issues.

Community
Advanced
jayhjenkinsjayhjenkins
1

root-cause-diagnosis

Diagnose metric anomaly root causes using 4-dimension segmentation and hypothesis testing.

Community
Basic