← All skills · Automation · Bug Diagnosis

Bug Diagnosis — finished output
Runs inClaude Code Codex Cursor Muse Dot Grok Bot Cue OpenClaw Hermes
Needs:The bug to diagnose: bug.txt (a Title line saying what broke, one Error line per error message — paste the exact message, do not paraphrase it — one Symptom line per observed behavior, one Context line per fact about what changed or where it runs, and optional Note lines).

Similar Skills

View all skills →

What you get

  • A ranked hypothesis list: each hypothesis with its signal count, matched evidence, and verification step
  • Intermittent and Regression flags, stated plainly
  • The verification step for the top hypothesis, so you start checking instead of guessing
  • Every gap, input error, and warning named in the report
  • No hypothesis matched? The report says so and asks for the exact error text

Good fit

  • Finding the most likely cause of a bug before changing any code
  • Getting the cheapest check that would prove or disprove each guess
  • Working through a bug top-down instead of trying fixes at random

Not for

  • Getting a root-cause verdict — a hypothesis is a guess to verify, not a diagnosis
  • Fixing the bug — this skill ranks guesses, the fix is yours after the check
  • Bugs with no error message and no context — the report will say so, not invent one

Sample output

An example of what this Skill produces. Sample content, shown for illustration.

Bug diagnosis — sample

Errors: 1 | Symptoms: 2 | Contexts: 2 | Hypotheses: 3 | Gaps: 0 | Errors: 0 | Warnings: 0

Ranked: 1. Null or undefined value at runtime — 3 signals ('cannot read propert', 'undefined', 'typeerror'); 2. Regression from a recent change — 2 signals ('worked yesterday', 'broke after'); 3. Race condition or ordering problem — 1 signal ('works locally').

Flags: Intermittent: no signal; Regression: yes — it worked before and broke after a change.

What this report is not: a hypothesis is a guess to verify, not a diagnosis — the report never names a root cause, only the check that would prove each guess.

About this Skill

You say
Checkout crashes after the deploy with a TypeError about undefined 'email' — what should I check first?

How to install

  1. Copy the install prompt into your agent: Read https://skillu.dev/install/agent.md, then install the Bug Diagnosis skill (bug-diagnosis).
  2. Or download the Skill package from this page after launch and place its folder in your agent’s skills directory.
  3. Call it with a slash command, e.g. /bug-diagnosis, and describe what you want in plain words.

FAQ

Does the top hypothesis mean that is the root cause?

No. It means that hypothesis matched the most signals in your error, symptoms, and context — it is the most worth checking first, not the most likely to be right. A real root cause with no signal in your text will not appear at all. Run the verification step; if it rules the guess out, move to the next one.

What if no hypothesis matches?

The report says so plainly and asks for the exact error text and more context. Add the full error message — pasted as it is, not paraphrased — plus what changed and where it runs, then re-run.

Get Premium access Browse more skills