skills.rest
juanjaragavi
juanjaragaviCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Enforces a four-phase systematic debugging workflow to reveal root causes before fixes.

Updated Dec 19, 2025
Search Tags:#debugging#defense-in-depth#systematic#tracing#phases#root-cause
One-click install
npx skills add https://github.com/juanjaragavi/topfinanzas-us-next --skill systematic-debugging-juanjaragavi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/juanjaragavi/topfinanzas-us-next/tree/main/.agents/skills/systematic-debugging
Command: npx skills add https://github.com/juanjaragavi/topfinanzas-us-next --skill systematic-debugging-juanjaragavi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill provides a structured, repeatable debugging methodology that enforces root-cause analysis before proposing fixes, reducing time wasted on symptom fixes and rework.

Core Features & Use Cases

  • Enforces the Four Phases (Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, Implementation)
  • Includes anti-patterns, defenses-in-depth, and guidance for reliable debugging under pressure
  • Supports tracing root causes through stack traces and multi-component systems, with references to related skills and testing procedures

Quick Start

Follow the four phases in order: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, then Implementation; complete Phase 1 before proposing fixes.

Frequently Asked Questions about systematic-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a systematic debugging workflow for finding root causes?▼

Systematic debugging enforces a four-phase workflow—Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation—to reveal underlying causes before applying fixes.

How do I stop fixing symptoms and start finding root causes in debugging?▼

To find root causes, you must complete the Root Cause Investigation phase entirely before proposing fixes, using pattern analysis and hypothesis testing to avoid symptom fixes and rework.

How do I trace root causes through stack traces in multi-component systems?▼

Trace root causes by following stack traces across multi-component systems during the investigation phase, applying pattern analysis to identify systemic issues before implementation.

What are common debugging anti-patterns I should avoid under pressure?▼

Common debugging anti-patterns include skipping root cause investigation and proposing fixes prematurely; applying defenses-in-depth and systematic phases prevents these pressure-induced errors.

What's the best way to structure a debugging process for complex software bugs?▼

The best way to structure debugging is using a four-phase system: investigate root causes, analyze patterns, test hypotheses, then implement fixes, supported by anti-pattern defenses for robust results.

Can I use systematic debugging for multi-component systems with complex stack traces?▼

Yes, systematic debugging supports tracing root causes through stack traces and multi-component systems, providing guidance for reliable debugging under pressure with cross-skill references.

Related Skills

Explore More Software Engineering Skills→
danmestasdanmestas
4

systematic-debugging

Trace bugs to root causes via phase-based investigation and call stack analysis.

Community
Advanced
Im5tuIm5tu
6

systematic-debugging

Identify root causes of software bugs through a four-phase debugging process.

Community
Advanced
lv7devlv7dev

debugging

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

Community
Advanced
decebaldecebal

ralph-tui-create-beads-rust

Convert a Markdown PRD into epic and child beads with dependencies for ralph-tui.

Community
Advanced