systematic-debugging

Guide developers through a four-phase root cause debugging process.

Updated Jun 19, 2025

Search Tags:#debugging #investigation #root cause #troubleshooting #error handling #bug fixing

Ready to run

npx skills add https://github.com/jonico22/api_business_jke --skill systematic-debugging-jonico22

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/jonico22/api_business_jke/tree/main/.agents/skills/systematic-debugging
Command: npx skills add https://github.com/jonico22/api_business_jke --skill systematic-debugging-jonico22

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill prevents wasted time and new bugs by ensuring you always find the root cause of an issue before attempting any fixes, especially under pressure.

Core Features & Use Cases

Systematic Four-Phase Process: Guides you through Investigation, Pattern Analysis, Hypothesis, and Implementation.
Root Cause Mandate: Strictly enforces finding the underlying issue, not just patching symptoms.
Pressure Resistance: Includes rules and language designed to prevent shortcuts during emergencies or time constraints.
Use Case: When a critical bug appears in production, use this Skill to methodically trace the issue to its origin, ensuring a permanent fix rather than a temporary workaround that might break later.

Quick Start

Use the systematic debugging skill to investigate any bug you encounter.

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 fixing symptoms?▼

To find the root cause of a bug, follow a structured four-phase process: Investigation, Pattern Analysis, Hypothesis testing, and Implementation, ensuring you trace the issue to its origin before applying fixes.

What is the best way to troubleshoot unexpected behavior under time pressure?▼

Troubleshooting under time pressure requires a systematic approach with strict rules to prevent shortcuts, ensuring thorough investigation and hypothesis testing to deliver a permanent fix rather than a temporary workaround.

How do I systematically debug complex issues in production?▼

Systematically debug complex production issues by methodically analyzing patterns and testing hypotheses, strictly enforcing root cause identification before any controlled implementation of fixes to prevent new bugs.

Why does patching symptoms lead to new bugs during error handling?▼

Patch symptoms during error handling leads to new bugs because the underlying issue remains unresolved, making a systematic investigation and root cause mandate essential for robust and permanent solutions.

Can I use a systematic debugging process for any software development scenario?▼

Yes, you can use a systematic debugging process for all software development scenarios, as it provides a structured framework for thorough investigation and pattern analysis regardless of the specific error context.

What are the steps to investigate a bug before attempting a fix?▼

The steps to investigate a bug involve a four-phase process: conducting a thorough Investigation, performing Pattern Analysis, forming a Hypothesis, and executing a controlled Implementation to ensure robust solutions.