skills.rest
esneiderbravo
esneiderbravoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Identifies root causes of bugs through a four-phase evidence-based debugging process.

1|Updated Apr 17, 2026
Search Tags:#debugging#investigation#defense-in-depth#patterns#trace#phases#root-cause
One-click install
npx skills add https://github.com/esneiderbravo/hackaton --skill systematic-debugging-esneiderbravo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/esneiderbravo/hackaton/tree/main/.github/skills/systematic-debugging
Command: npx skills add https://github.com/esneiderbravo/hackaton --skill systematic-debugging-esneiderbravo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging helps engineers identify the root cause of bugs and avoid patching symptoms, saving time and reducing rework.

Core Features & Use Cases

  • Four-phase process with explicit gates to ensure root-cause investigation before fixes
  • Evidence gathering, pattern analysis, and defensive practices like traceability and defense-in-depth
  • Real-world guidance for handling pressure scenarios, and integration with related skills and references

Quick Start

Load the skill and start with Phase 1: Root Cause Investigation before proposing any 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 bug instead of just patching symptoms?▼

Systematic debugging identifies root causes by enforcing a four-phase process with evidence gathering and pattern analysis before fixes. It prevents symptom patches by applying explicit investigation gates and defense-in-depth practices.

What is the best way to debug production bugs under time pressure?▼

The best way to debug production bugs under time pressure is to follow a structured four-phase process that prioritizes root-cause investigation. Real-world guidance helps handle pressure scenarios while ensuring fixes target the actual problem.

How do I systematically trace integration issues and test failures?▼

You trace integration issues and test failures by applying a four-phase debugging process that emphasizes evidence gathering and pattern analysis. This method ensures you track the root cause across software projects rather than applying quick fixes.

Does systematic debugging work for performance problems and integration issues?▼

Yes, systematic debugging applies to performance problems, integration issues, test failures, and production bugs across software projects. It uses defense-in-depth and root-cause tracing to handle these varied scenarios effectively.

When should I not use a root-cause debugging approach for my software?▼

You should avoid root-cause debugging when a rapid symptom patch is strictly required for immediate mitigation and the long-term reduction of rework is not a priority. It is designed to save time overall by preventing recurring issues.

Related Skills

Explore More Software Engineering Skills→
alexanderopalexanderop
4

systematic-debugging

Diagnose software bugs through a four-phase root-cause investigation process.

Community
Basic
dmulcaheydmulcahey

systematic-debugging

Trace software bugs to root causes using a four-phase investigation methodology.

Community
Advanced
lidge-junlidge-jun
5

systematic-debugging

Guide root cause analysis through investigation, pattern analysis, hypothesis testing, and implementation phases.

Community
Advanced
valtterimelkkovaltterimelkko
1

systematic-debugging

Investigate root causes through a four-phase debugging framework before modifying code.

Community
Advanced