bug-hunt

Guides users through bug reproduction, root-cause identification, and regression testing.

2|Updated Sep 20, 2025

Search Tags:#debugging #regression #software-engineering #reproduction #bug-hunt #tests-first

Ready to run

npx skills add https://github.com/anortham/sherpa --skill bug-hunt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bug-hunt
Source: https://github.com/anortham/sherpa/tree/main/skills/bug-hunt
Command: npx skills add https://github.com/anortham/sherpa --skill bug-hunt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces reproduction-first debugging to prevent symptom-fixing and ensure root-cause fixes.

Core Features & Use Cases

Reproduce & Isolate: Reproduce the bug manually and isolate minimal reproduction cases.
Capture in Test: Create a failing test that captures the exact bug behavior.
Fix & Verify: Implement root-cause fixes and verify with tests.
Regression Prevention: Add tests to prevent similar bugs in the future.

Quick Start

Begin with a guide check, switch to Bug Hunt, reproduce the bug, write a failing test, fix the root cause, run the full test suite, and add regression tests.

Frequently Asked Questions about bug-hunt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I reproduce a bug systematically before fixing it?▼

Reproducing bugs systematically means creating a minimal case that reliably triggers the issue, isolating it from surrounding code. This ensures you're fixing the root cause, not just hiding symptoms. Start by documenting exact steps, inputs, and environment conditions that trigger the failure.

Why should I write a test that captures a bug before fixing it?▼

Writing a failing test before the fix documents the exact bug behavior and serves as verification once you've corrected the root cause. It also prevents regressions—the same bug won't slip back in during future changes because the test will catch it.

What's the difference between symptom-fixing and root-cause debugging?▼

Symptom-fixing masks the visible error without addressing what caused it, leaving the underlying issue to resurface elsewhere. Root-cause debugging traces the failure to its source, so one fix resolves the problem durably and prevents related regressions.

How do I prevent the same bug from happening again?▼

After fixing the root cause, add regression tests that verify the specific bug scenario stays fixed. These tests act as guards in your test suite, catching any future change that would reintroduce the same problem.

When should I use a reproduction-first approach to debugging?▼

Use reproduction-first debugging for any bug report, error investigation, or regression. It's especially critical when fixing issues in production or in code with complex dependencies, where a wrong fix can create cascading problems.