Agent skill · research science · sickn33
bug-hunt-swarm
Parallel read-only multi-agent root-cause investigation for bugs, regressions, crashes, flaky behavior, or unexplained failures.
Why this skill is useful
Provides a structured multi-agent approach for diagnosing bugs that includes specific roles and evidence-gathering techniques not commonly known to AI.
What it needs
About 4k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Bug Hunt Swarm When to Use Use this skill when you need parallel read-only multi-agent root-cause investigation for bugs, regressions, crashes, flaky behavior, or unexplained failures. Use when the user asks to investigate a bug, find the root cause, trace a regression, understand why something broke, or wants a ranked diagnosis with the... Investigate a bug with four read-only sub-agents in parallel, then have the main agent rank the likely causes and recommend the fastest path to prove or fix the issue. This skill is diagnosis-first: do not edit files or implement fixes as part of this workflow. Step 1: Build the Bug Packet Start by collecting the smallest useful investigation packet: 1. Symptom 2. Expected behavior 3. Actual behavior 4. Reproduction steps, if known 5. Scope of impact 6. Relevant evidence, such as logs, stack traces, failing tests, screenshots, recent diffs, or environment details Prefer this source order: 1. Direct user description 2. Explicit files, stack traces, logs, tests, or screenshots provided by the user 3. Current git changes or recent repo history when the bug appears regression-like 4. The smallest relevant code path or subsystem surrounding the failure If the bug report is underspecified, infer a minimal problem statement and say what is still unknown. Before launching sub-agents, read the closest project instructions and relevant docs for the touched area, such as: AGENTS.md repo workflow docs architecture, state, routing, schema, or runtime docs for the affected subsystem Step 2: Bound the Investigation Write a short investigation brief for the swarm: 1. What appears broken 2. What is not yet proven 3. What part of the system is most likely involved 4. What evidence already exists 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/bug-hunt-swarm--673eeb