skills.rest
FaisalAlqarni
FaisalAlqarniCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Guide structured four-phase debugging with evidence gathering and hypothesis testing.

5|Updated Feb 6, 2026
Search Tags:#debugging#investigation#root cause#troubleshooting#error handling#bug fixing
One-click install
npx skills add https://github.com/FaisalAlqarni/sp-ecc --skill systematic-debugging-faisalalqarni
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/FaisalAlqarni/sp-ecc/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/FaisalAlqarni/sp-ecc --skill systematic-debugging-faisalalqarni

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 or symptom-based patching, ensuring that the true root cause of any issue is identified and resolved.

Core Features & Use Cases

  • Systematic 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 specific language and rules to prevent rationalization under time pressure.
  • Use Case: When a critical bug appears in production, this Skill ensures a thorough investigation is conducted before any fixes are applied, preventing further instability.

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
What is the best way to find the root cause of a bug instead of just fixing symptoms?▼

Systematic debugging prevents symptom-fixing by mandating a four-phase process: Investigation, Pattern Analysis, Hypothesis, and Implementation. This structured approach ensures you gather evidence and test hypotheses before applying any fixes, resolving the fundamental issue reliably.

How do I systematically debug complex systems when a critical bug appears in production?▼

To systematically debug complex systems, you must conduct a thorough investigation gathering evidence before applying any fixes. This structured process prevents further instability by identifying the true root cause rather than patching immediate symptoms under time pressure.

Why does quick fixing bugs often cause new bugs and wasted time?▼

Quick fixes cause new bugs because they address immediate symptoms rather than the true root cause. Symptom-based patching without thorough investigation and evidence gathering leads to wasted time and introduces further instability into the system.

Can I use this systematic debugging approach under tight production deadlines?▼

Yes, this debugging approach includes specific pressure resistance rules and language designed to prevent rationalization under time pressure. It ensures thorough investigation is conducted before fixes are applied, even during critical production incidents.

When should I avoid quick fixes and start a formal troubleshooting investigation?▼

You should start a formal troubleshooting investigation whenever unexpected behavior or bugs appear, before proposing any fixes. This prevents the wasted time and new bugs caused by symptom-based patching in complex systems.

Related Skills

Explore More Software Engineering Skills→
knowz-ioknowz-io
1

knowzcode-telemetry

Correlate Sentry and App Insights telemetry to diagnose production errors.

Official
Intermediate
lionbenjaminlionbenjamin
15

fix

Diagnose and fix codebase bugs with root-cause analysis and regression tests.

Community
Advanced
grafanagrafana
535

debug-with-grafana

Diagnoses application issues using Grafana metrics, logs, and traces.

Official
Advanced
openaeonopenaeon
87

systematic-debugging

Investigate software bugs through a four-phase root-cause workflow with evidence gathering.

Community
Intermediate