systematic_debugging

Guide software bug root cause analysis through investigation, pattern analysis, hypothesis testing, and implementation.

Updated Aug 23, 2026

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

Ready to run

npx skills add https://github.com/maddhruv/cuttlefish --skill systematic-debugging-maddhruv

💬 Prompt for ChatGPT / Claude Chat▼

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

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 solutions, ensuring that the true root cause of any technical issue is identified and resolved.

Core Features & Use Cases

Systematic Investigation: Guides users through a structured four-phase process (Investigation, Pattern Analysis, Hypothesis, Implementation) to ensure thorough debugging.
Pressure Resistance: Provides explicit rules and anti-patterns to counteract rationalizations made under time pressure or urgency.
Use Case: When a critical bug appears in production, this Skill ensures the agent doesn't just apply a quick patch but systematically finds and fixes the underlying issue, preventing recurrence.

Quick Start

Use the systematic_debugging skill to investigate any bug or unexpected behavior 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 the symptom?▼

To find the root cause of a bug, you need a systematic debugging process that investigates patterns, tests hypotheses, and implements fixes. This prevents wasted time on quick patches that cause new bugs or allow recurrence.

What is the best way to debug critical production issues under time pressure?▼

The best way to debug critical production issues under time pressure is to follow explicit anti-pattern rules that resist rationalizations. This ensures you perform thorough multi-component tracing and defense-in-depth validation rather than applying quick patches.

How do I systematically troubleshoot an error across multiple components?▼

To systematically troubleshoot an error across multiple components, follow a four-phase process: investigation, pattern analysis, hypothesis testing, and implementation. This structured approach traces issues accurately and validates fixes deeply.

Why does my bug fix keep causing new bugs in my software?▼

Your bug fix keeps causing new bugs because of symptom-based solutions. Applying a structured root cause analysis process ensures you identify and resolve the true underlying technical issue instead of patching surface-level effects.

Can I use a structured debugging process for any technical issue or only production bugs?▼

You can use this structured debugging process for any technical issue or unexpected behavior. It guides you through pattern analysis and hypothesis testing to ensure the underlying problem is resolved regardless of severity.