systematic-debugging

Guide four-phase root cause analysis for debugging technical issues.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/andrescardonas7/salchipapa-web --skill systematic-debugging-andrescardonas7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/andrescardonas7/salchipapa-web/tree/main/.cursor/skills/systematic-debugging
Command: npx skills add https://github.com/andrescardonas7/salchipapa-web --skill systematic-debugging-andrescardonas7

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a robust framework to systematically identify and resolve the root cause of any bug, test failure, or unexpected behavior, preventing the common pitfalls of quick fixes and symptom-based patching.

Core Features & Use Cases

  • Four-Phase Process: Guides users through Investigation, Pattern Analysis, Hypothesis, and Implementation.
  • Root Cause Mandate: Emphasizes finding the fundamental issue, not just addressing immediate symptoms.
  • Pressure Resistance: Includes rules and language designed to prevent shortcuts under time pressure or when a quick fix seems obvious.
  • Use Case: When a critical test fails in CI, instead of guessing or adding arbitrary waits, use this Skill to methodically trace the failure back to its origin, ensuring a permanent fix and preventing recurrence.

Quick Start

Use the systematic debugging skill to investigate the current test failure.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is the best way to find the root cause of a bug instead of just fixing symptoms?

Root cause analysis is best achieved through a structured, four-phase debugging methodology covering investigation, pattern identification, hypothesis testing, and implementation to ensure permanent fixes and prevent recurrence.

How do I debug a failing test in CI without guessing or adding arbitrary waits?

Debug a failing test by applying a systematic investigation process that traces the failure back to its origin through pattern analysis and hypothesis testing, ensuring a permanent resolution rather than a quick patch.

How do I resist time pressure when troubleshooting unexpected software behavior?

Resist time pressure during troubleshooting by following a structured methodology with specific rules designed to prevent shortcuts and common rationalizations when a quick fix seems obvious.

What are the steps to systematically investigate unexpected software behavior?

Systematic investigation involves four phases: investigating the issue, identifying patterns, testing hypotheses, and implementing the fix, with a strict mandate to address the fundamental problem over immediate symptoms.

Can I use this debugging methodology for any software development bug?

This debugging methodology is applicable to all software development bugs, test failures, and unexpected behaviors, providing a robust framework to systematically identify and resolve issues across any technical context.