skills.rest
DuveSalo
DuveSaloCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Guide structured four-phase debugging to identify and resolve root causes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill prevents time-wasting "quick fixes" that mask underlying issues and lead to more bugs. It ensures you systematically identify and resolve the true root cause of any bug or unexpected behavior.

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 any fixes are applied.
  • Pressure Resistance: Includes rules and language designed to prevent shortcuts under time pressure.
  • Use Case: When a critical production bug appears, use this Skill to ensure a thorough investigation, preventing superficial fixes that could cause further issues.

Quick Start

Use the systematic-debugging skill when encountering any bug or unexpected behavior before proposing any fixes.

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 when should I use it?▼

Systematic debugging is a structured process to identify and resolve the root cause of bugs. You should use it when encountering unexpected behavior before proposing any fixes, ensuring thorough investigation over symptom masking.

How do I find the root cause of a bug instead of just fixing symptoms?▼

To find the root cause of a bug, follow a structured four-phase process: Investigation, Pattern Analysis, Hypothesis, and Implementation. This enforces finding the origin of the issue before applying any fixes.

How can I prevent taking debugging shortcuts under time pressure?▼

To prevent debugging shortcuts under time pressure, use a systematic approach with specific rules and anti-patterns designed to resist rationalization. This ensures complete investigation and prevents superficial quick fixes.

What is the best way to troubleshoot a critical production bug?▼

The best way to troubleshoot a critical production bug is using a systematic debugging process. This ensures thorough investigation and pattern analysis, preventing superficial fixes that could cause further issues.

Why does fixing symptoms lead to more bugs?▼

Fixing symptoms leads to more bugs because it masks underlying issues without resolving the true root cause. Systematic debugging prevents this time-wasting approach by enforcing thorough investigation before implementation.

Related Skills

Explore More Software Engineering Skills→
The-RabakThe-Rabak

reproduce-bug

Coordinate bug reproduction across logs, console output, and browser screenshots.

Community
Intermediate
tomguntomgun

fixing-bugs

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

Community
Intermediate
m19803261706m19803261706

cx-fix

Investigate, fix, test, and commit code changes with conventional commits.

Community
Intermediate
pagopapagopa
1

TechAISystematicDebugging

Enforces root-cause investigation before proposing fixes for technical issues.

Official
Advanced