Skills / development-and-testing
bug-hunter
Systematically finds and fixes bugs using proven debugging techniques. Traces from symptoms to root cause, implements fixes, and prevents regression.
new
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:
# Application logs
tail -f logs/app.log
# System logs
journalctl -u myapp -f
# Browser console
# Open DevTools → Console tab
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 formSubscribers only
The full skill, its 2 bundled files and every download is included with every paid Complete AI plan.
Details
| Source | community |
|---|---|
| License | — |
| Risk label | safe ("critical" means the skill may run commands or touch files — read before use) |
| Files | README.md, SKILL.md |
| Added | 2026-03-05 |
Related skills
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
debugging-strategies
Transform debugging from frustrating guesswork into systematic problem-solving with proven strategies, powerful tools, and methodical approaches.
openclaw-github-repo-commander
7-stage super workflow for GitHub repo audit, cleanup, PR review, and competitor analysis
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
test-fixing
Systematically identify and fix all failing tests using smart grouping strategies. Use when explicitly asks to fix tests ("fix these tests", "make tests pass"), reports test failures ("tests are failing", "test suite is broken"), or completes implementation and wants tests passing.
