Skip to content
Skillpedia
Testing48k · #2463

bug-hunter

Helps your agent find and fix code errors systematically. It traces problems to their origin and prevents them from returning.

What it does

This tool helps find and fix errors in computer code. It follows clues to discover the problem's cause, fixes it, and makes sure it doesn't return.

When to use it

  • ✓When something in the program isn't working as expected.
  • ✓If you receive a strange error message.
  • ✓When the program behaves unexpectedly.

Example of what to ask your AI

“I found an error on my website, can you help me figure out what's wrong?”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/bug-hunter/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/bug-hunter/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

The tool first tries to make the error happen on purpose to understand what's going on. Then, it gathers information, like error messages and logs, to guess the cause and test that guess.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add sickn33/agentic-awesome-skills --skill bug-hunter

Or download just the file:

curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/bug-hunter/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

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 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.login(userData);
console.log('After API call:', response);

Use debugger:

debugger; // Execution pauses here
const result = processData(input);

Isolate the problem:

// Comment out code to narrow down
// const result = complexFunction();
const result = { mock: 'data' }; // Use mock data

5. Find Root Cause

Trace back to the actual problem:

Common root causes:

  • Null/undefined values
  • Wrong data types
  • Race conditions
  • Missing error handling
  • Incorrect logic
  • Off-by-one errors
  • Async/await issues
  • Missing validation

Example trace:

Symptom: "Cannot read property 'name' of undefined"
↓
Where: user.profile.name
↓
Why: user.profile is undefined
↓
Why: API didn't return profile
↓
Why: User ID was null
↓
Root cause: Login didn't set user ID in session

6. Implement Fix

Fix the root cause, not the symptom:

Bad fix (symptom):

// Just hide the error
const name = user?.profile?.name || 'Unknown';

Good fix (root cause):

// Ensure user ID is set on login
const login = async (credentials) => {
  const user = await authenticate(credentials);
  if (user) {
    session.userId = user.id; // Fix: Set user ID
    return user;
  }
  throw new Error('Invalid credentials');
};

7. Test the Fix

Verify it actually works:

1. Reproduce the original bug
2. Apply the fix
3. Try to reproduce again (should fail)
4. Test edge cases
5. Test related functionality
6. Run existing tests

8. Prevent Regression

Add a test so it doesn't come back:

test('login sets user ID in session', async () => {
  const user = await login({ email: 'test@example.com', password: 'pass' });
  
  expect(session.userId).toBe(user.id);
  expect(session.userId).not.toBeNull();
});

Debugging Techniques

Binary Search

Cut the problem space in half repeatedly:

// Does the bug happen before or after this line?
console.log('CHECKPOINT 1');
// ... code ...
console.log('CHECKPOINT 2');
// ... code ...
console.log('CHECKPOINT 3');

Rubber Duck Debugging

Explain the code line by line out loud. Often you'll spot the issue while explaining.

Print Debugging

Strategic console.logs:

console.log('Input:', input);
console.log('After transform:', transformed);
console.log('Before save:', data);
console.log('Result:', result);

Diff Debugging

Compare working vs broken:

  • What changed recently?
  • What's different between environments?
  • What's different in the data?

Time Travel Debugging

Use git to find when it broke:

git bisect start
git bisect bad  # Current commit is broken
git bisect good abc123  # This old commit worked

…
FAQ

What is a 'bug'?

A 'bug' is an error or flaw in a computer program that causes it to not work correctly.

How does the tool find the cause of an error?

It uses techniques like following the steps that cause the error, analyzing error messages and logs, and testing guesses (hypotheses) to find the problem's origin.

What does 'prevent regression' mean?

It means ensuring that the fixed error doesn't reappear in the future, usually by adding a test to check if the fix works.

Details

Original description by the author

Systematically finds and fixes bugs using proven debugging techniques. Traces from symptoms to root cause, implements fixes, and prevents regression.

repo: sickn33/agentic-awesome-skills

Popularity

GitHub stars
48k
Ranking position
#2463
License
MIT
Updated
10/15/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills