Bughunt Skill — Testing skill for Claude Code
Agent skill that plays your app or game like real users (seeded personas), checks invariants every step, and turns each failure into a replayable bundle, regression test and root-cause fix.
How to install Bughunt Skill
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open cskwork/bughunt-skill and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Bughunt Skill does
Agent skill that plays your app or game like real users (seeded personas), checks invariants every step, and turns each failure into a replayable bundle, regression test and root-cause fix. Godot, native iOS, web.
Alternatives in Testing
- Develop Web Game — Build and test web games iteratively using Playwright with time-stepping 14.6k ★
- Deslop Reborn — One iteration of the IronClaw Reborn de-slop loop — take ONE Reborn crate, fan out parallel review sub-agents 12.6k ★
- Fixtests — Systematic test failure analysis and remediation 849 ★
README
bughunt — an agent skill that plays your app until it breaks
[](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/overview) [](LICENSE)
Unit tests and a fresh-game autoplay pass can both be green while a real player hits a bug in the first minute: the first command after "Continue" is rejected, an AI acts before its screen is visible, a finished player's save comes back to life. These bugs live on **transitions**, and only show up when someone plays the way people actually play.
`bughunt` makes an agent do that playing for you: seeded **personas** drive the shipped build through its real input paths, **invariant oracles** check every step, and every failure becomes a replayable bundle, a regression test, and a root-cause fix.
What it does
- Build the target as shipped (exported / simulator build, not only the editor).
- Run seeded personas: new player, button masher, save → quit → resume at every phase, background / foreground interruptions, slow player who lets timers expire, speed changer, random tapper, other languages, small and large screens, Reduce Motion.
- Check oracles at every step: no errors or crashes, every enabled command accepted on the first try, no AI action before its screen is ready, UI inside the safe area with no overlap, sane state (no negative currency, no vanished units), deterministic replay of the same seed, no softlock, persisted state round-trips and stays eligible.
- On failure: save seed + action log + screenshot + state dump → minimise → regression test → root-cause fix → replay the whole matrix.
- Stop when every persona × seed passes twice in a row; report the evidence.
Adapters: **Godot** (in-game QA runner driven by command-line flags), **native iOS** (XCUITest / Maestro), **web** (Playwright). App profiles fit the personas and oracles to the product: **game**, **CRUD app** (rec
Related Skills
Logic Locate
Locate the root cause of a confirmed failure — use when you have a stack trace, failing test, or wrong output
Systematic Debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase frame
Analyze Test Report
Phân tích test report — automation (Playwright/Allure/JUnit/TestNG) hoặc manual (execution_report.md / retest_
Al Debug
Root-cause a bug/test failure/race condition before fixing; checks and maintains a project-local known-issues
Hatch3r Bug Pipeline
Run a known-cause bug fix through a 3-phase test-first pipeline -- reproduce + root-cause, regression-test + f
J Debug
Systematic bug investigation — root cause analysis, not random fixes. Use when a test fails, a bug appears, or
Related Agents
Research Users
User research specialist. Plans studies, writes interview and usability test guides, builds personas and journ
Godot Game Architect
Game Analyst
Game-design feasibility analyst. Takes game-researcher output + project context (Godot 4, solo dev, tactical R