skills.rest
rafaelcalleja
rafaelcallejaCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Diagnose software issues using a four-phase systematic debugging framework.

2|1|Updated Oct 11, 2025
Search Tags:#debugging#problem solving#systematic approach#troubleshooting#bug fixing#hypothesis testing#software testing
One-click install
npx skills add https://github.com/rafaelcalleja/claude-market-place --skill systematic-debugging-rafaelcalleja
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/rafaelcalleja/claude-market-place/tree/main/plugins/claudekit-skills/skills/debugging/systematic-debugging
Command: npx skills add https://github.com/rafaelcalleja/claude-market-place --skill systematic-debugging-rafaelcalleja

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Haphazard debugging leads to frustration and missed bugs. This skill provides a methodical, step-by-step framework to systematically identify and resolve software issues, ensuring thoroughness and efficiency.

Core Features & Use Cases

  • Structured Approach: Guides through a clear sequence of steps: reproduce, isolate, analyze, fix, verify.
  • Hypothesis Testing: Encourages forming and testing hypotheses to efficiently narrow down the problem space.
  • Test-Driven Debugging: Integrates testing principles to confirm fixes and prevent regressions.
  • Pressure Testing Scenarios: Provides examples for debugging under various stress conditions, ensuring robustness.
  • Use Case: Debug a complex intermittent bug by first reproducing it reliably, then systematically isolating the faulty component, analyzing its behavior, and verifying the fix with targeted tests.

Quick Start

Use the systematic-debugging skill to help me debug an intermittent bug in my Python application.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
How do I debug an intermittent bug systematically?▼

Systematic debugging uses a four-phase framework: reproduce the bug reliably, isolate the faulty component, analyze its behavior patterns, and implement a fix with verification. This structured approach uncovers root causes rather than masking symptoms, ensuring thorough resolution of intermittent issues.

What's the difference between fixing symptoms and finding root causes?▼

Symptom fixes mask problems temporarily; root-cause debugging identifies the underlying issue. The systematic framework enforces hypothesis testing and evidence gathering to distinguish true causes from surface manifestations, preventing regressions and recurring failures.

Can I use systematic debugging for production incidents and performance problems?▼

Yes. The framework applies to bugs, test failures, production incidents, performance degradation, and build or integration problems. It enforces disciplined investigation across all technical issues requiring thorough diagnosis before implementation.

How do I integrate testing into my debugging workflow?▼

Test-driven debugging confirms fixes and prevents regressions by embedding testing principles into the systematic framework. After isolating and fixing issues, targeted tests verify the solution and ensure the problem doesn't recur.

What happens if I skip steps in the debugging process?▼

The framework includes non-skippable phases and anti-shortcut guardrails to enforce thoroughness. Skipping investigation or pattern analysis leads to incomplete diagnosis, missed root causes, and wasted time on ineffective fixes.

Related Skills

Explore More Software Engineering Skills→
drafaeldrafael
3

debug-error

Diagnose and fix software errors through systematic root cause analysis.

Community
Advanced
shekerkammashekerkamma

investigate

Systematically debugs software errors by tracing root causes before implementing fixes.

Community
Advanced
franroafranroa

Debugging Wizard

Diagnose software errors using systematic root-cause analysis and testing.

Community
Advanced
gajjalaashok75-UIgajjalaashok75-UI
2

error-debugging-error-analysis

Analyze logs, stack traces, and failure patterns to diagnose application errors.

Community
Advanced