debug-issue

Diagnose software bugs by identifying root causes and delivering minimal, testable fixes.

Updated Mar 17, 2026

Search Tags:#debugging #evidence #error-handling #root-cause #hypotheses #stack-trace #failing-tests

Ready to run

npx skills add https://github.com/saboteur-labs/ai-workflows --skill debug-issue-saboteur-labs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug-issue
Source: https://github.com/saboteur-labs/ai-workflows/tree/main/skills/coding/debug-issue
Command: npx skills add https://github.com/saboteur-labs/ai-workflows --skill debug-issue-saboteur-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Systematically diagnose and fix bugs, errors, or unexpected behaviour in code. Use this skill when something is broken and you need to find the root cause — especially when given an error message, stack trace, a failing test, or a description of unexpected behaviour. Also use when the user says "this isn't working", "I'm getting an error", "why does this happen", "help me debug", or "the tests are failing".

Core Features & Use Cases

Structured debugging workflow that guides root-cause analysis, hypothesis formation, evidence gathering, and minimal, verifiable fixes.
Works across languages and environments, leveraging error outputs, tests, and logs to drive fixes.
Useful when users report disruption or failures and need a reproducible debugging process.

Quick Start

Describe symptoms, identify the root cause, and implement a minimal, testable fix.

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 bug from a stack trace?▼

Finding the root cause of a bug from a stack trace requires a structured debugging workflow that collects evidence, forms hypotheses, and isolates the failing component before applying a minimal, testable patch.

What is the best way to debug failing tests in my codebase?▼

Debugging failing tests is best handled by analyzing error outputs and logs to form hypotheses, then implementing a verifiable fix that directly addresses the root cause rather than just treating the symptom.

Can I use a structured debugging process for vague error descriptions?▼

Yes, a structured debugging process can diagnose vague error descriptions by systematically gathering evidence and testing hypotheses across languages and environments to pinpoint the root cause.

How do I fix unexpected behavior in software when I don't know what's broken?▼

Fixing unexpected behavior involves identifying the root cause through structured evidence collection and hypothesis testing, then delivering a minimal patch that can be verified against the reported issue.

Does this debugging approach work across different programming languages?▼

Yes, this debugging approach works across languages and environments by leveraging universal debugging artifacts like error messages, stack traces, tests, and logs to drive root-cause analysis and verifiable fixes.

Why should I use a structured debugging workflow instead of just patching the error?▼

A structured debugging workflow ensures you identify the actual root cause through evidence collection and hypothesis testing, delivering a minimal, testable patch that prevents the bug from recurring rather than masking the symptom.