debug

Trace software defects through systematic investigation and root cause analysis.

1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/docaohieu2808/claude-skills --skill debug-docaohieu2808
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/docaohieu2808/claude-skills/tree/main/debug
Command: npx skills add https://github.com/docaohieu2808/claude-skills --skill debug-docaohieu2808

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pypdf, pdfplumber, pdf2image, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a structured framework to systematically investigate and resolve bugs, test failures, and unexpected behavior by prioritizing root cause analysis over quick fixes.

Core Features & Use Cases

  • Systematic Debugging: A four-phase process (Investigation, Pattern Analysis, Hypothesis, Implementation) to ensure thorough problem-solving.
  • Root Cause Tracing: Techniques to trace errors backward through call stacks to pinpoint the origin of invalid data.
  • Defense-in-Depth: Strategies to add validation at multiple layers, making bugs structurally impossible.
  • Verification Protocol: Ensures that fixes are validated with evidence before claiming completion.
  • Use Case: When a critical test fails unexpectedly, use this Skill to guide the investigation, identify the exact cause, implement a robust fix, and verify its effectiveness.

Quick Start

Use the debug skill to systematically investigate the recent test failure.

Frequently Asked Questions about debug

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

FAQPage Schema
What is the best way to perform systematic root cause analysis for an unexpected test failure?▼

It employs a four-phase systematic debugging process: Investigation, Pattern Analysis, Hypothesis, and Implementation, ensuring thorough bug resolution and defense-in-depth validation across any programming language.

How do I trace unexpected software behavior back to its origin using call stack analysis?▼

You trace unexpected behavior by analyzing the call stack to identify the exact origin of invalid data, applying multi-layer validation strategies to make the bug structurally impossible to reproduce.

Can I use this systematic debugging framework across all programming languages and tech stacks?▼

Yes, the debugging framework is applicable to bugs, test failures, and performance issues across all programming languages, providing language-agnostic techniques for root cause tracing and strict verification.

Does the debugging framework support validating fixes with evidence before claiming completion?▼

Yes, the framework includes a strict verification protocol that requires validating fixes with concrete evidence before claiming issue resolution, ensuring reliable and robust software defect elimination.

What should I do when quick bug fixing approaches fail to resolve persistent performance issues?▼

When quick fixes fail, you should employ systematic debugging phases to investigate the root cause of performance issues, adding defense-in-depth validation at multiple layers to ensure reliable issue resolution.