debug

Guide evidence collection, hypothesis testing, and verification for software debugging.

7|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/hhellbusch/my-ai-workspace --skill debug-hhellbusch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/hhellbusch/my-ai-workspace/tree/main/.agents/skills/debug
Command: npx skills add https://github.com/hhellbusch/my-ai-workspace --skill debug-hhellbusch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a structured approach for in-depth debugging of complex problems, guiding systematic investigation and evidence gathering.

Core Features & Use Cases

  • Methodical Investigation Protocols: Activates investigation workflows with evidence collection, hypothesis testing, and verification.
  • Domain Expertise Detection: Detects domain-specific knowledge requirements and loads relevant expertise for targeted debugging.
  • Comprehensive Guidance: Offers principles, techniques, and step-by-step methods for scientific root cause analysis in software debugging scenarios.

Quick Start

Run the debugging skill when encountering persistent, hard-to-reproduce bugs, and follow the guided protocols to identify the true root causes.

Frequently Asked Questions about debug

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

FAQPage Schema
What is systematic root cause analysis for complex software debugging?▼

Systematic root cause analysis is a structured debugging method that guides evidence collection, hypothesis formation, testing, and verification to accurately identify the true origins of complex software issues across codebases and environments.

How do I debug persistent or hard-to-reproduce bugs systematically?▼

To debug hard-to-reproduce bugs systematically, follow guided investigation protocols that enforce evidence collection, form targeted hypotheses, test variables methodically, and verify the root cause before applying a permanent fix.

Can I use this structured debugging method across different codebases and environments?▼

Yes, this structured debugging method applies across diverse codebases and environments by detecting domain-specific knowledge requirements and loading relevant contextual expertise to guide targeted investigation.

What's the best way to investigate complex software issues without guessing?▼

The best way to investigate complex software issues without guessing is to apply scientific root cause analysis principles, relying on disciplined evidence collection and hypothesis testing rather than trial-and-error assumptions.

When should I use a systematic debugging workflow instead of standard troubleshooting?▼

You should use a systematic debugging workflow when encountering persistent, complex bugs where standard troubleshooting fails, requiring structured evidence collection and hypothesis verification to pinpoint the actual root cause.