| name | bug-hunter |
| description | Systematically finds and fixes bugs using proven debugging techniques. Traces from symptoms to root cause, implements fixes, and prevents regression. |
| type | skill |
| created | 2026-02-27T00:00:00.000Z |
| domain | ai-ml |
| category | ml-data-science |
| risk | safe |
| source | community |
| tags | ["skill","ai-ml","ml-data-science","bug","hunter"] |
Bug Hunter
Systematically hunt down and fix bugs using proven debugging techniques. No guessing—follow the evidence.
When to Use This Skill
- User reports a bug or error
- Something isn't working as expected
- User says "fix the bug" or "debug this"
- Intermittent failures or weird behavior
- Production issues need investigation
The Debugging Process
1. Reproduce the Bug
First, make it happen consistently:
1. Get exact steps to reproduce
2. Try to reproduce locally
3. Note what triggers it
4. Document the error message/behavior
5. Check if it happens every time or randomly
If you can't reproduce it, gather more info:
- What environment? (dev, staging, prod)
- What browser/device?
- What user actions preceded it?
- Any error logs?
2. Gather Evidence
Collect all available information:
Check logs:
tail -f logs/app.log
journalctl -u myapp -f
Check error messages:
- Full stack trace
- Error type and message
- Line numbers
- Timestamp
Check state:
- What data was being processed?
- What was the user trying to do?
- What's in the database?
- What's in local storage/cookies?
3. Form a Hypothesis
Based on evidence, guess what's wrong:
"The login times out because the session cookie
expires before the auth check completes"
"The form fails because email validation regex
doesn't handle plus signs"
"The API returns 500 because the database query
has a syntax error with special characters"
4. Test the Hypothesis
Prove or disprove your guess:
Add logging:
console.log('Before API call:', userData);
const response = await api.(userData);
.(, response);
