hunt
Finds root cause before applying fixes for errors, crashes, regressions, failing tests, broken behavior, and screenshot-reported defects. Use when users report in any language errors, crashes, broken behavior, regressions, failing tests, screenshot evidence, or something that used to work and now fails. Not for code review or new features.
Profile →npx skills add tw93/Waza --skill hunt --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Hunt: Diagnose Before You Fix Prefix your first line with 🥷 inline, not as its own paragraph. A patch applied to a symptom creates a new bug somewhere else. ## Outcome Contract - Outcome: the root cause is identified before any fix is applied. - Done when: one sentence explains the cause, every observed symptom fits it, and the fix or handoff is verified against a reproducible check. - Evidence: source trace, repro command or UI path, logs or state, targeted test/build output, and runtime evidence for UI or native defects. - Output: root cause, fix or handoff, verification result, and any unswept sibling risks. - Authorization: "diagnose", "investigate", "why", "look into", "排查", "看看", or equivalent is report-only. Apply a fix only when the current turn explicitly asks to fix, change, implement, or optimize; root-cause proof is still required first. **Do not touch code until you can state the root cause in one sentence:** > "I believe the root cause is [X] because [evidence]." Name a specific file, function, line, or condition. "A state management issue" is not testable. "Stale cache in `useUser` at `src/hooks/user.ts:42` because the dependency array is missing `userId`" is test
- Outcome Contract
- Diagnosis Signals
- Durable Context Preflight
- Hard Rules
- Fix Scope Discipline
- Bisect Mode
- Repeated Regression / Screenshot Reference Mode
- Scope Blast Mode
- Confirm or Discard
- Runtime Evidence Ladder
- Native App Freeze Mode
- Targeted Logging
- Gotchas
- Rendering Bug Mode
What does the hunt skill do?
Finds root cause before applying fixes for errors, crashes, regressions, failing tests, broken behavior, and screenshot-reported defects. Use when users report in any language errors, crashes, broken behavior, regressions, failing tests, screenshot evidence, or something that used to work and now fails. Not for code review or new features.
How do I install it?
Run `npx skills add tw93/Waza --skill hunt --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From tw93/Waza, a repository with 6,760 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.