systematic-debugging

Guide users through a four-phase debugging process for root cause analysis.

Updated Jun 23, 2024

Search Tags:#testing #debugging #root cause #troubleshooting #bug fixing #systematic process

Ready to run

npx skills add https://github.com/KyleLeduc/bulk-video-review --skill systematic-debugging-kyleleduc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/KyleLeduc/bulk-video-review/tree/main/.github/skills/systematic-debugging
Command: npx skills add https://github.com/KyleLeduc/bulk-video-review --skill systematic-debugging-kyleleduc

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 a problem before attempting any fixes, especially under pressure.

Core Features & Use Cases

Systematic Investigation: Guides you through a 4-phase process (Investigation, Pattern Analysis, Hypothesis, Implementation) to methodically uncover the source of bugs.
Pressure Resistance: Provides explicit rules and anti-patterns to combat rushed decisions and symptom-fixing temptations.
Use Case: When a critical test fails or a production bug appears, load this Skill to ensure you don't just apply a quick patch, but thoroughly understand and fix the underlying issue, saving hours of future debugging.

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

What is a systematic debugging process for finding the root cause of bugs?▼

A systematic debugging process enforces evidence gathering and root cause analysis before proposing solutions. It guides you through four phases: investigation, pattern analysis, hypothesis testing, and implementation to methodically uncover and fix the source of technical issues.

How do I fix a failing test without just patching the symptom?▼

To fix a failing test properly, follow a structured investigation process that mandates evidence gathering and pattern analysis before implementation. This prevents rushed decisions and ensures you identify and resolve the underlying root cause rather than applying a quick symptom patch.

What's the best way to debug production bugs under time pressure?▼

The best way to debug production bugs under time pressure is to use explicit rules and anti-patterns that combat rushed decisions. A systematic approach ensures you gather evidence and analyze root causes first, preventing new bugs and saving hours of future troubleshooting.

Can I use a systematic troubleshooting approach for unexpected application behavior?▼

Yes, you can apply a systematic troubleshooting approach to unexpected application behavior. It supports debugging various issue types by guiding you through pattern analysis and hypothesis testing to uncover why the unexpected behavior occurs before implementing a fix.

Why does my bug fix keep introducing new problems?▼

Your bug fix keeps introducing new problems because you are likely fixing symptoms without finding the root cause. Applying a systematic debugging process ensures thorough evidence gathering and root cause analysis before implementation, preventing wasted time and avoiding new bugs.

When should I avoid quick patches during software troubleshooting?▼

You should avoid quick patches during software troubleshooting whenever you encounter test failures or production bugs. Using a structured debugging process with mandated hypothesis testing ensures you fully understand the underlying issue before attempting any fixes.