systematic-debugging

Investigate software bugs through four phases before implementing fixes.

7|Updated Dec 7, 2025

Search Tags:#testing #debugging #investigation #root cause #troubleshooting #bug fixing

Ready to run

npx skills add https://github.com/ftzi/livespec --skill systematic-debugging-ftzi

💬 Prompt for ChatGPT / Claude Chat▼

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

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 by ensuring that the root cause of any issue is identified and fixed, rather than just addressing the immediate symptom.

Core Features & Use Cases

Systematic Investigation: Guides users through a four-phase process (Investigation, Pattern Analysis, Hypothesis, Implementation) to uncover the fundamental reason for a bug or failure.
Pressure Resistance: Includes specific language and rules designed to prevent shortcuts and rationalizations, especially under time pressure or when a quick fix seems obvious.
Use Case: When a test fails unexpectedly, instead of guessing or applying a quick patch, you load this skill to systematically trace the error, identify the exact faulty logic, and implement a robust fix.

Quick Start

Use the systematic debugging skill to investigate any bug or test failure 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?▼

Systematic debugging enforces root cause investigation before any fixes are applied. It guides you through a four-phase methodology: Investigation, Pattern Analysis, Hypothesis formation, and Implementation, ensuring you fix the faulty logic rather than the symptom.

What is the best way to debug unexpected software failures and test errors?▼

The best way to debug unexpected test failures is to follow a structured investigation process. Instead of guessing or applying quick patches, you systematically trace the error, analyze patterns, form a hypothesis about the exact faulty logic, and implement a robust fix.

How do I prevent quick fixes and shortcuts when troubleshooting under time pressure?▼

To prevent shortcuts when troubleshooting under time pressure, use a debugging methodology with specific rules and anti-patterns designed to resist rationalizations. This ensures you maintain systematic investigation and hypothesis testing even when a quick fix seems obvious.

What are the steps to systematically trace a software bug?▼

Systematically tracing a software bug involves four sequential steps: thoroughly investigating the issue, analyzing failure patterns, forming a hypothesis about the root cause, and implementing a verified fix. This prevents new bugs caused by hasty patching.

Can I use systematic debugging for any software component or behavior issue?▼

Yes, you can use systematic debugging for any software component. It is designed to address bugs, test failures, and unexpected behavior across all software systems by mandating a thorough investigation of the underlying logic before implementation.