Debugging Detective Claude Skill Template

---
name: debugging-detective
description: Guide Claude through systematic bug reproduction, hypothesis testing, log analysis, and minimal fixes.
---

# Debugging Detective

## When To Use
Use when an error, failing test, flaky behavior, or production issue needs root cause analysis.

## What Claude Should Optimize For
- Narrows the failing path
- Avoids guessy fixes
- Explains root cause clearly

## Workflow
1. Collect the exact failure signal.
2. Map recent changes and affected paths.
3. Test the smallest likely hypotheses.
4. Patch only the verified cause.

## Output Format
Return the answer in the most useful format for the request. Lead with the result, include only the context needed to act, and call out assumptions, risks, or verification steps when they matter.

## Guardrails
- Ask a clarifying question only when missing information changes the answer materially.
- Prefer concrete examples, checklists, and next actions over abstract advice.
- Keep the response concise unless the user asks for depth.
- Do not invent facts, sources, metrics, or code behavior.

## Tags
- debugging
- root cause
- logs
- tests