debug

Debug software issues systematically with root-cause analysis and verification.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/MinhHoangDono/antigravity-kit --skill debug-minhhoangdono
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/MinhHoangDono/antigravity-kit/tree/main/.agent/skills/debug
Command: npx skills add https://github.com/MinhHoangDono/antigravity-kit --skill debug-minhhoangdono

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Prevents wasted time and repeated regressions by guiding you to systematically identify the true cause of failures or unexpected behavior before applying changes.

Core Features & Use Cases

  • Systematic Debugging: Walks through investigation phases for bugs, test failures, and build issues.
  • Root Cause Tracing: Targets problems deep in the call stack to pinpoint the initiating failure.
  • Layered Validation & Verification: Confirms the fix at multiple layers and avoids claiming success prematurely.
  • System & CI/CD Diagnostics: Handles server errors, pipeline failures, and performance degradation with the right reference playbooks.
  • Tool-Assisted Investigation: Supports common debugging surfaces like logs/CI output and database diagnostics.

Use Case: Your CI job fails with an obscure stack trace after a dependency bump; use this skill to trace the error source, validate the corrected behavior, and ensure the issue is truly resolved.

Quick Start

Ask the AI to run a systematic debug on the provided error details, identify the most likely root cause, then propose a fix that includes verification steps.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I find the root cause of a CI/CD pipeline failure?

To find the root cause of a CI/CD pipeline failure, systematically trace the initiating failure deep in the call stack using log analysis before applying changes. This approach stops repeated regressions by verifying the corrected behavior through structured investigation phases.

What is systematic debugging and when do I need it for software errors?

Systematic debugging is a structured investigation process that traces root causes of code bugs, test failures, and server errors. You need it to stop repeated regressions and incorrect fixes by confirming the resolution at multiple layers before claiming the problem is resolved.

How do I debug an obscure stack trace after a dependency bump?

Debug an obscure stack trace after a dependency bump by running a systematic debug on the error details to identify the most likely root cause. Propose a fix that includes layered validation and verification steps to ensure the issue is truly resolved.

Can I use root cause analysis for database performance diagnostics?

Yes, you can use root cause analysis for database performance diagnostics by selecting the appropriate reference playbook. This handles performance degradation and database-related issues by pinpointing the initiating failure and confirming the fix through tool-assisted investigation.

What is the best way to verify a code fix before claiming it is resolved?

The best way to verify a code fix is through layered validation that confirms the corrected behavior at multiple levels. This avoids claiming success prematurely and ensures the root cause of the failure or unexpected behavior is truly resolved.