skills.rest
huhuimike85
huhuimike85COMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Guide users through a four-phase root cause analysis process for technical issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill prevents wasted time and new bugs caused by random fixes or symptom-based patching, ensuring you always address the underlying root cause of any technical issue.

Core Features & Use Cases

  • Four-Phase Process: Guides you through Investigation, Pattern Analysis, Hypothesis, and Implementation.
  • Root Cause Mandate: Enforces finding the origin of a bug before proposing any fixes.
  • Pressure Resistance: Provides explicit rules and anti-patterns to resist time pressure and rationalization.
  • Use Case: When a critical API endpoint starts returning errors, use this skill to systematically trace the issue from the error message back to the faulty code, ensuring a permanent fix rather than a temporary workaround.

Quick Start

Use the systematic-debugging skill to investigate any bug 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 patching the symptoms?▼

To find the root cause of a bug, mandate a thorough investigation before implementation using a four-phase process: Investigation, Pattern Analysis, Hypothesis, and Implementation to prevent wasted time and symptom-based patching.

What is the best way to systematically debug production bugs and test failures?▼

Systematically debug production bugs and test failures by tracing the issue from the error message back to the faulty code, enforcing root cause analysis to ensure a permanent fix rather than a temporary workaround.

How do I avoid common debugging shortcuts when under time pressure?▼

Avoid debugging shortcuts under time pressure by following explicit rules and anti-patterns designed to resist rationalization, enforcing the identification of a bug's origin before proposing fixes to prevent new bugs.

What steps should I follow to troubleshoot performance problems systematically?▼

Troubleshoot performance problems systematically through four phases: Investigation, Pattern Analysis, Hypothesis, and Implementation, ensuring you address the underlying root cause of the technical issue.

Why does random fixing often cause new bugs during troubleshooting?▼

Random fixing causes new bugs during troubleshooting because it relies on symptom-based patching rather than addressing the underlying root cause, a problem a systematic investigation process prevents.

Related Skills

Explore More Software Engineering Skills→
htlin222htlin222
77

error-detective

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

Community
Intermediate
tomguntomgun

fixing-bugs

Reproduce bugs with regression tests and apply minimal root-cause fixes.

Community
Intermediate
SeifBenayedSeifBenayed
114

debug

Trace root causes of application errors and test failures using stack traces and git history.

Community
Intermediate
kk20300113-pngkk20300113-png

investigate

Guide structured root-cause debugging for software errors and regressions.

Community
Advanced