Bug hunt

Skill yeaight7/agent-powerups/skills/bug-hunt

Curated power-ups for coding agents: skills, slash commands, MCP configs, hooks, AGENTS.md templates, and workflows for serious software engineering. Claude Code, Codex, Antigravity CLI, Cursor and more

Install

npx -y skills add yeaight7/agent-powerups --skill bug-hunt

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when reproducing, isolating, and fixing a bug with the smallest safe change.

SKILL.md

1.6 KB, as published. Nobody here has run it

Purpose

Locate and fix the root cause of a bug with minimal scope. A correct fix beats a fast guess.

When to Use

A specific, reproducible bug needs fixing.
A test is failing and the cause is unclear.
An unexpected behavior needs a targeted fix.

For complex, persistent, or multi-component bugs, use systematic-debugging instead.

Inputs

Bug description or reproduction steps.
Relevant error messages or stack traces.
Access to the codebase and test suite.

Workflow

Reproduce — Trigger the bug reliably before writing any code.
Identify — Find the true failing layer, not just the first place the error surfaces.
Fix — Apply the minimal change at the root cause.
Test — Add or update a focused test that would have caught this bug.

Output

Root cause: <what caused the bug>
Fix: <what was changed and where>
Verification: <how the fix was confirmed>
Residual risk: <any edge cases not covered>

Verification

Bug reproduced before fix was written
Root cause identified (not just symptom location)
Fix is minimal — no unrelated changes bundled in
Test added or updated to prevent regression

Failure Modes

Fixing the symptom — Error location ≠ root cause. Trace backward until the origin is found.
Skipping reproduction — Fixes written without a reliable reproduction often miss the actual bug.
Missing test — Without a regression test, the same bug is likely to return.