hunt

Diagnose root causes of bugs using hypothesis-driven evidence validation.

6.8k|402|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/tw93/Waza --skill hunt-tw93
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt
Source: https://github.com/tw93/Waza/tree/main/plugins/waza/skills/hunt
Command: npx skills add https://github.com/tw93/Waza --skill hunt-tw93

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineers often struggle to identify the root cause of bugs, regressions, and flaky behavior before applying fixes, leading to wasted effort and repeated repairs.

Core Features & Use Cases

  • Structured hypothesis-driven debugging: formulate robust root-cause hypotheses supported by observable evidence.
  • Durable context and evidence flow: collect logs, traces, environment details, and symptom lists to justify conclusions.
  • Clear handoff and verification: deliver a concise root-cause statement, proposed fix, and an actionable verification plan.

Quick Start

Describe the observed symptoms and reproduce steps, then I will propose a one-sentence root-cause hypothesis and verification plan.

Frequently Asked Questions about hunt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the root cause of a flaky bug before applying a fix?

To find the root cause of a flaky bug, you need a hypothesis-driven debugging workflow that validates explicit evidence like logs and traces. This approach enforces a three-stage validation process before any repair.

What is the best way to structure root-cause analysis for runtime errors and crashes?

The best way to structure root-cause analysis is by formulating a one-sentence hypothesis supported by observable evidence, symptom lists, and environment state. This method ensures your conclusions are justified.

How do I handle a bug handoff to a verification team with clear repro steps?

To handle a bug handoff to a verification team, provide a concise root-cause statement, a proposed fix, and an actionable verification plan. This ensures the team understands the exact reproduction steps.

Can I diagnose screenshot-reported defects using a hypothesis-driven debugging workflow?

Yes, you can diagnose screenshot-reported defects by extracting observable symptoms and mapping them to environment state and traces. The workflow applies structured hypothesis validation across software projects.

Why should I gather logs and environment state before fixing a software regression?

Gathering logs and environment state before fixing a software regression prevents wasted effort on repeated repairs. Durable context flow justifies your conclusions and supports a robust root-cause hypothesis.