bug-hunter
Systematically finds and fixes bugs using proven debugging techniques. Traces from symptoms to root cause, implements fixes, and prevents regression.
Profile →npx skills add sickn33/agentic-awesome-skills --skill bug-hunter --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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:** ```bash # 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 stor
- When to Use This Skill
- The Debugging Process
- 1. Reproduce the Bug
- 2. Gather Evidence
- 3. Form a Hypothesis
- 4. Test the Hypothesis
- 5. Find Root Cause
- 6. Implement Fix
- 7. Test the Fix
- 8. Prevent Regression
- Debugging Techniques
- Binary Search
- Rubber Duck Debugging
- Print Debugging
Application logs tail -f logs/app.log System logs journalctl -u myapp -f Browser console Open DevTools → Console tab git bisect start git bisect bad # Current commit is broken git bisect good abc123 # This old commit worked Git will check out commits for you to test
What does the bug-hunter skill do?
Systematically finds and fixes bugs using proven debugging techniques. Traces from symptoms to root cause, implements fixes, and prevents regression.
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill bug-hunter --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.