skills.rest
mezivillager
mezivillagerCOMMUNITY
Explore all skills by this author →
GitHub

systematic_debugging

Guide four-phase debugging from investigation through implementation.

1|Updated Mar 3, 2026
Search Tags:#debugging#root cause#troubleshooting#bug fixing#error resolution#systematic process
One-click install
npx skills add https://github.com/mezivillager/hacer --skill systematic-debugging-mezivillager
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic_debugging
Source: https://github.com/mezivillager/hacer/tree/main/.claude/skills/systematic-debugging
Command: npx skills add https://github.com/mezivillager/hacer --skill systematic-debugging-mezivillager

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 that only address symptoms, ensuring that the true root cause of any technical issue is identified and resolved systematically.

Core Features & Use Cases

  • Four-Phase Process: Guides users through Investigation, Pattern Analysis, Hypothesis, and Implementation.
  • Root Cause Mandate: Emphasizes finding the fundamental issue before any fixes are applied.
  • Pressure Resistance: Includes specific rules and language to prevent shortcuts under time pressure or urgency.
  • Use Case: When a critical API endpoint starts returning errors, this Skill ensures you don't just add a temporary workaround, but systematically trace the problem back to its origin, preventing recurrence.

Quick Start

Use the systematic debugging skill to investigate any bug or unexpected behavior before proposing fixes.

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 software bug instead of just fixing the symptom?▼

Systematic debugging prevents quick fixes by enforcing a four-phase process: investigation, pattern analysis, hypothesis testing, and implementation. This ensures you resolve the fundamental issue before applying any code changes.

What is the best way to troubleshoot a critical API endpoint returning unexpected errors?▼

The best way to troubleshoot a critical API endpoint returning errors is systematically tracing the problem back to its origin through investigation and pattern analysis, rather than applying a temporary workaround under pressure.

How do I systematically debug technical issues when facing extreme time pressure?▼

Systematically debug technical issues under time pressure by applying specific anti-patterns and pressure-resistant rules that mandate thorough root cause analysis, preventing shortcuts even when urgency is high.

Does systematic debugging work for operational issues or is it only for software development bugs?▼

Systematic debugging works for all software development and operational issues. The four-phase methodology is applicable to any technical problem requiring root cause analysis rather than temporary symptom suppression.

What are the limitations of using a symptom-fixing approach for error resolution?▼

The limitation of symptom-fixing for error resolution is wasted time and the introduction of new bugs. A systematic root cause mandate ensures you identify and resolve the fundamental issue first.

Related Skills

Explore More Software Engineering Skills→
FoundationForgeFoundationForge

debug

Run structured debugging sessions to reproduce, isolate, and diagnose software errors.

Official
Intermediate
tomguntomgun

fixing-bugs

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

Community
Intermediate
troykellytroykelly
11

ci-monitoring

Monitor CI pipelines, diagnose failures, and document fixes until green.

Community
Advanced
lv7devlv7dev

debugging

Investigate root causes before implementing fixes through a four-phase debugging workflow.

Community
Advanced