systematic-debugging

Guide four-phase root cause analysis for technical issues.

Updated Mar 8, 2026

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

Ready to run

npx skills add https://github.com/nuts-and-bolts-ai/nanoclaw-cheerful --skill systematic-debugging-nuts-and-bolts-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/nuts-and-bolts-ai/nanoclaw-cheerful/tree/main/groups/slack_cheerful-dev/.claude/skills/systematic-debugging
Command: npx skills add https://github.com/nuts-and-bolts-ai/nanoclaw-cheerful --skill systematic-debugging-nuts-and-bolts-ai

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 that the root cause of any technical issue is identified and addressed before any fixes are implemented. It provides a structured, pressure-resistant process for debugging.

Core Features & Use Cases

Mandatory Root Cause Analysis: Enforces a strict four-phase process (Investigation, Pattern Analysis, Hypothesis, Implementation) that must be completed before proposing fixes.
Pressure Resistance: Includes specific language and rules designed to prevent shortcuts under time pressure or when a "quick fix" seems obvious.
Use Case: When a critical API is failing in production, instead of immediately trying a known "quick fix" like adding a retry, this Skill guides you through a systematic investigation to find the underlying reason for the failure, preventing future occurrences and more complex issues.

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

What is systematic debugging and when should I use it?▼

Systematic debugging is a structured methodology to find the root cause of technical issues. You should use it for any software bug or unexpected behavior to prevent wasted time and avoid new bugs from quick fixes.

How do I find the root cause of a bug instead of just fixing symptoms?▼

To find the root cause, follow a strict four-phase process: Investigation, Pattern Analysis, Hypothesis Formation, and Implementation. This methodology ensures you address the underlying issue rather than applying superficial symptom fixes.

How can I resist taking shortcuts when fixing critical production outages under time pressure?▼

Use a debugging methodology with specific rules designed to resist time pressure and common rationalizations. It enforces completing root cause analysis before proposing any fixes, preventing impulsive quick fixes during critical outages.

What is the best way to troubleshoot a failing API without introducing new bugs?▼

The best way to troubleshoot a failing API is through systematic investigation to find the underlying reason for the failure. This structured approach prevents future occurrences and more complex issues compared to applying immediate quick fixes like adding retries.

Does systematic debugging work for all software development issues and test failures?▼

Yes, systematic debugging is applicable to all software development and operational issues. It provides a structured, pressure-resistant process that works effectively for everything from isolated test failures to critical production outages.