systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: liauw-media

Debug software bugs through reproduce, isolate, identify, fix, and verify phases.

3|2|Updated Oct 10, 2025

Search Tags:#code analysis #debugging #systematic approach #troubleshooting #root cause analysis #bug fixing #error resolution

Ready to run

npx skills add https://github.com/liauw-media/CodeAssist --skill systematic-debugging-liauw-media

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the frustration and wasted time of random debugging by providing a methodical, 5-step process to reliably reproduce, isolate, identify the root cause, fix, and verify bugs, ensuring permanent solutions and deeper system understanding.

Core Features & Use Cases

5-Step Debugging Process: Guides you through Reproduce, Isolate, Identify, Fix, and Verify phases, ensuring a systematic approach to every bug.
Root Cause Identification: Focuses on finding the underlying cause, not just symptoms, preventing recurring bugs and building deeper system understanding.
Use Case: When a user reports "Login sometimes fails," this skill will guide you to reliably reproduce the bug, isolate it to a specific code line, identify the root cause (e.g., missing database table), implement a proper fix, and verify it doesn't break anything else.

Quick Start

I'm encountering a bug where user profiles show incorrect data. Use the systematic-debugging skill to help me find and fix the issue.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

How do I debug a bug systematically instead of guessing at fixes?▼

Systematic debugging follows a 5-step process: reproduce the bug reliably, isolate it to specific code or conditions, identify the root cause rather than symptoms, implement a targeted fix, and verify it works without breaking other functionality. This approach prevents recurring bugs and builds deeper system understanding.

What's the best way to find the root cause of a bug instead of just fixing the symptom?▼

Root cause analysis digs beneath surface symptoms to uncover the underlying issue. By isolating conditions where the bug occurs and tracing the code path, you identify why it happens, enabling permanent fixes that prevent the problem from reoccurring in different contexts.

How do I reproduce a bug that happens inconsistently or in production?▼

Reliable reproduction requires documenting exact conditions, user actions, environment state, and data that trigger the bug. By methodically recreating these conditions, you move from random failures to predictable, testable scenarios that reveal the root cause.

Can I use systematic debugging for flaky tests, performance regressions, and API failures?▼

Yes. Systematic debugging applies to any unexpected behavior: login failures, flaky tests, performance regressions, and user-reported issues across web applications, APIs, services, and production environments. The 5-step workflow ensures reproducibility and root-cause identification for all bug types.

What should I verify after fixing a bug to ensure it's truly resolved?▼

Verification confirms the fix resolves the original issue and doesn't introduce regressions. Test the specific bug scenario, run existing test suites, and audit related code paths to ensure the fix is permanent and doesn't break adjacent functionality.

Why does isolating a bug matter before implementing a fix?▼

Isolation narrows the problem to specific code, data, or conditions, preventing blind fixes that mask symptoms without addressing causes. Targeted isolation enables precise, efficient fixes that resolve the actual issue rather than papering over it.