bug-detective

Diagnose code errors from error messages, logs, and stack traces.

2|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Clay-HHK/claude-config --skill bug-detective-clay-hhk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-detective
Source: https://github.com/Clay-HHK/claude-config/tree/main/skills/bug-detective
Command: npx skills add https://github.com/Clay-HHK/claude-config --skill bug-detective-clay-hhk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Helps developers and engineers systematically diagnose and resolve code errors, exceptions, and failing behavior by turning scattered symptoms into a clear, evidence-driven debugging plan.

Core Features & Use Cases

  • Structured Debugging Workflow: Guides users through understanding the problem, gathering evidence, forming hypotheses, verifying causes, and applying fixes.
  • Error Pattern Recognition: Identifies common error types (syntax, import, type, attribute, key/index, null reference, network, permission, resource) and recommends targeted methods.
  • Practical Tools & Examples: Provides stack-trace analysis techniques, binary search, logging/breakpoint strategies, language-specific patterns for Python, JavaScript/TypeScript, and shell, plus checklists and example scripts for real-world debugging tasks.

Quick Start

Ask the bug-detective to analyze the exact error message, stack trace, file and line, reproduction steps, and environment details, then provide a prioritized hypothesis list and step-by-step verification plan.

Frequently Asked Questions about bug-detective

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

FAQPage Schema
How do I diagnose a Python or JavaScript error from a stack trace?

To debug a runtime failure, provide the exact error text, reproduction steps, and environment details. The system applies a structured workflow to form prioritized hypotheses, verify root causes, and return actionable fixes for your code.

What's the best way to troubleshoot a runtime failure when I only have scattered error logs?

Troubleshooting a runtime failure with scattered logs involves transforming those symptoms into an evidence-driven debugging plan. By inputting available log text and environment details, you receive a structured workflow to identify error patterns and verify root causes.

Can I use this to find the root cause of exceptions across different programming languages?

Yes, you can find the root cause of exceptions across Python, JavaScript/TypeScript, and shell scripts. The system recognizes common error patterns like syntax, import, type, and network issues, applying language-specific techniques to isolate the failure.

Does troubleshooting a production error require specific environment details?

Troubleshooting a production error requires collecting exact error text, file and line locations, reproduction steps, and environment details. Supplying these inputs ensures the diagnostic analysis generates accurate hypotheses and targeted verification steps.

How do I fix code errors when the root cause is not obvious from the error message?

To fix code errors when the root cause is hidden, apply error pattern recognition and binary search strategies. The system guides you through gathering evidence, forming hypotheses, and applying targeted methods to systematically isolate the underlying failure.