From bugbash
Use when the user wants to find bugs, stress-test, QA, exploratory-test, or verify behavior by exercising the running system—not for routine implementation, refactors, or fix-focused debugging unless they ask to switch modes after findings exist.
How this skill is triggered — by the user, by Claude, or both
Slash command
/bugbash:using-bugbashThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Bugbash is **not** a general development methodology. It is a **narrow contract**: spend effort **proving** whether the software misbehaves, under **clear boundaries**, with **evidence** you could hand to another engineer.
Bugbash is not a general development methodology. It is a narrow contract: spend effort proving whether the software misbehaves, under clear boundaries, with evidence you could hand to another engineer.
Bugbash fits when the user (or parent agent) wants things like: bug bash, QA pass, stress test, break it, edge cases, negative testing, soak, concurrency worries, release confidence.
Usually a mismatch: pure code review without running anything, architecture debates, “why is this slow” deep profiling, or step-by-step debugging where the user already has a stack trace and wants a fix.
bugbash-core first—keep it short.bugbash-core with the Skill tool and run it at the intensity the user asked for (quick, standard, or deep). Default to standard if unspecified.bugbash-api and bugbash-ui together, then merge into one tracker.CLAUDE.md, AGENTS.md, and direct instructions win. If the user forbids network, shell, or destructive actions, obey and say what could not be exercised.
In Claude Code, load skills with the Skill tool rather than reading skill files ad hoc.
npx claudepluginhub riwaht/claude-bugbash --plugin bugbashHunts cross-component bugs in assembled features by dispatching 5 parallel adversarial test dimensions against the full diff. Use for integration issues, wiring faults, and state mismatches between tasks.
Conducts time-boxed exploratory testing sessions using heuristics to uncover bugs, edge cases, invalid data issues, and undocumented behaviors, with structured documentation.