agentleFS
Sign inStart free
yeaight7yeaight7/agent-powerups/skills/bug-hunt/SKILL.md

bug-hunt

Skill6 starsChanged 4 months agoApache-2.0View on GitHub

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

22 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use learn, ship and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • genomewalkerSkill

    learn

    Learn from web sources, generate SKILL.md, and store key patterns in soul memory. Trigger keywords: learn, skill-gen, web-learn, documentation, tutorial.

    Also in 3 projects that use this

  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 3 projects that use this

  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 3 projects that use this

The file

Create a free account to mount
Files
SKILL.md

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

  1. Reproduce — Trigger the bug reliably before writing any code.
  2. Identify — Find the true failing layer, not just the first place the error surfaces.
  3. Fix — Apply the minimal change at the root cause.
  4. 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free