bug-hunter
Investigate and fix bugs systematically. Use when debugging issues or tracing errors.
When & Why to Use This Skill
Bug Hunter is a systematic Claude skill designed to streamline the software debugging and error-tracing process. By utilizing a structured five-step workflow—Reproduce, Locate, Trace, Fix, and Document—it empowers developers to resolve complex technical issues efficiently using integrated command-line tools like Bash and Grep.
Use Cases
- Case 1: Systematically reproducing reported software bugs by executing test commands and documenting discrepancies between expected and actual behavior.
- Case 2: Rapidly locating error origins in large-scale codebases using recursive search and pattern matching tools.
- Case 3: Performing root cause analysis by tracing call stacks and investigating recent code changes via git history.
- Case 4: Implementing verified bug fixes through a Test-Driven Development (TDD) approach, ensuring regressions are prevented.
- Case 5: Generating comprehensive bug fix reports that document the issue, root cause, and verification steps for team knowledge sharing.
| name | bug-hunter |
|---|---|
| description | Investigate and fix bugs systematically. Use when debugging issues or tracing errors. |
| allowed-tools | Bash, Read, Grep, Glob |
Bug Hunter
Version: 1.0.0 Purpose: Systematic bug investigation and resolution
Workflow
Step 1: Reproduce
# Run failing test/command
npm test
Document:
- Expected behavior
- Actual behavior
- Error message
Step 2: Locate
# Search for error
grep -r "error message" src/
Step 3: Trace
- Find error origin
- Trace call stack
- Identify root cause
Step 4: Fix
- Write failing test
- Implement fix
- Verify test passes
Step 5: Document
## Bug Fix Report
**Issue**: [Description]
**Root Cause**: [Explanation]
**Fix**: [What was changed]
**Test**: [How to verify]
Tips
- Check recent commits:
git log --oneline -20 - Look for similar issues:
git log --grep="bug" - Binary search:
git bisect