agentleFS
Sign inStart free
Nexus-Organization-InfosecNexus-Organization-Infosec/ClaudeSkills/bug-hunt/SKILL.md

bug-hunt

Skill1 starsChanged 3 months agoNo licenceView on GitHub

Proactively hunt the codebase for bugs of every size — major reliability bugs (connection/network failures, missing timeouts, unhandled disconnects, no retry/reconnect, crashes on the hot path, data corruption, money/precision errors), correctness/logic bugs and edge cases, and tiny issues (small security nits, defensive gaps) noticed in passing. Rank findings by severity, then fix them safely. Invoked as "bug-hunt" for one normal hunt, or "bug-hunt N" (e.g. "bug-hunt 10") for N successive hunt rounds, each sweeping a fresh area and fixing what it finds. Also combines with work-until-limit to hunt continuously until the usage ceiling. Use whenever the user invokes /bug-hunt or asks to "hunt for bugs", "find bugs in my project", "what's broken or fragile here", or "look for connection issues and crashes". Think adversarially: what inputs and conditions break this?

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

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