systematic-debugging

Trace, analyze, and resolve bugs through a four-phase systematic debugging workflow.

Updated Mar 30, 2026

Search Tags:#debugging #defense-in-depth #systematic #tracing #phases #root-cause

Ready to run

npx skills add https://github.com/nashirabbash/autorepychatbot --skill systematic-debugging-nashirabbash

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bugs and unreliable fixes waste time and mask root causes. This skill provides a disciplined, four-phase approach to identify the true cause before proposing any changes, reducing rework and chaos.

Core Features & Use Cases

Phase-driven process: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation to ensure robust fixes.
Defense-in-depth mindset: validates data and behavior across multiple layers to prevent regression.
Practical guidance for high-pressure scenarios (time pressure, stakeholders) to avoid shortcut fixes.
Real-world workflows: tracing, testing, and documenting root causes for future prevention.

Quick Start

Follow the four phases starting with Root Cause Investigation to uncover the true cause before implementing any changes.

Frequently Asked Questions about systematic-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is a systematic approach to debugging and finding root causes?▼

Systematic debugging enforces a four-phase workflow: root-cause investigation, pattern analysis, hypothesis testing, and implementation with validation gates. This disciplined process identifies the true cause of bugs before proposing changes, reducing rework and preventing regressions.

How do I fix recurring bugs and prevent regressions across code paths?▼

To fix recurring bugs and prevent regressions, apply a defense-in-depth validation approach during the implementation phase. This technique validates data and behavior across multiple layers, ensuring fixes address the true root cause rather than masking symptoms.

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

Tracing and resolving a bug systematically involves four phases: start with root-cause investigation, perform pattern analysis, conduct hypothesis and testing, then implement the fix. Explicit stop gates between phases ensure robust, regression-free resolutions.

How do I avoid shortcut fixes when debugging under time pressure?▼

To avoid shortcut fixes under time pressure, follow a disciplined debugging workflow with explicit stop gates. This process provides practical guidance for high-pressure scenarios with stakeholders, enforcing root-cause investigation before implementation to prevent unreliable patches.

When should I use hypothesis testing in my debugging workflow?▼

Use hypothesis testing during the third phase of systematic debugging, immediately after pattern analysis. This step validates theories about the root cause before moving to implementation, preventing unnecessary code changes and ensuring the fix addresses the actual fault.