debug_issue

Identify root causes of defects before applying fixes.

41|10|Updated Jan 24, 2026

Search Tags:#workflow #debugging #quality #root-cause #software #reproduction

Ready to run

npx skills add https://github.com/krishnakanthb13/antigravity_global_skills --skill debug-issue-krishnakanthb13

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug_issue
Source: https://github.com/krishnakanthb13/antigravity_global_skills/tree/main/debug_issue
Command: npx skills add https://github.com/krishnakanthb13/antigravity_global_skills --skill debug-issue-krishnakanthb13

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Root-cause debugging protocol that prevents fixes without investigation, reducing patch churn and false fixes.

Core Features & Use Cases

Isolation and symptom analysis to distinguish between expected vs observed behavior.
Reproduction and Minimal Reproducible Example (MRE) creation to reliably reproduce failures.
Systematic root-cause investigation, instrumentation, and hypothesis testing.
Guided implementation with guardrails to prevent over-fixes and regressions.
Verification and regression checks to ensure fixes address root cause.

Quick Start

Describe the issue and follow the 5-step Iron Law workflow to identify root cause before fixing.

Frequently Asked Questions about debug_issue

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

FAQPage Schema

How do I find the root cause of a software defect before applying a fix?▼

To find the root cause of a software defect, you must systematically isolate the issue, analyze symptoms, and create a minimal reproducible example to reliably reproduce the failure before attempting any code changes.

What is the best way to stop recurring bugs and false fixes during incident response?▼

The best way to stop recurring bugs and false fixes during incident response is to enforce a structured debugging protocol that requires hypothesis testing and root-cause verification before applying patches, thereby reducing patch churn.

How do I create a minimal reproducible example for reliable bug reproduction?▼

To create a minimal reproducible example for bug reproduction, you systematically isolate the failing behavior from expected observations and strip away extraneous code until the defect triggers consistently in a controlled environment.

What inputs do I need to start a structured root-cause analysis workflow?▼

To start a structured root-cause analysis workflow, you need to provide a clear issue description and relevant application logs to establish a reproducible baseline for distinguishing between expected and observed behavior.

How does guided implementation prevent regressions when fixing code?▼

Guided implementation prevents regressions by applying development guardrails during the fix phase, ensuring the code change targets the verified root cause without introducing over-fixes or new software defects.

When should I use a systematic debugging protocol instead of quick patching?▼

You should use a systematic debugging protocol instead of quick patching when you experience patch churn or recurring incidents, as it enforces verification and regression checks to ensure fixes address the true root cause.