Diagnose a stack trace
Turns a stack trace plus a short description of what you were doing into ranked hypotheses, the first checks to run for each, and what extra evidence would settle it.
Prompts are text you copy into your own assistant. KitLocal does not run them.
Fill in the variables
What you type stays in this browser. It is not added to the URL, saved, or sent anywhere.
Preview
Still needed: Stack trace, What were you doing / what changed
Help me diagnose this error. Runtime: . Reproducible: Unknown.
What I was doing / what changed:
{{situation}}
Stack trace:
```
{{stackTrace}}
```
Respond with:
1. A one-sentence reading of what the exception says (not a guess about the cause).
2. Up to four hypotheses ranked by likelihood. For each: why the trace supports it, and the
single quickest check that would confirm or rule it out.
3. The extra evidence you would ask for (logs, versions, inputs) if none of the checks settle it.
4. Only then, a suggested fix for the most likely hypothesis.
Mark anything you are unsure about as "unverified". Do not claim a root cause you cannot see.
Purpose
Move from a wall of stack frames to a short list of testable hypotheses.
When to use it
- An exception appears and the cause is not obvious from the top frame.
- You want a disciplined checklist instead of guessing.
What to prepare
- The full stack trace, including "Caused by" sections.
- What you were doing, what changed recently, and whether it is reproducible.
Expected output
A numbered Markdown answer following the four sections above.
About this catalog
Bundled snapshot · published Nov 15, 2026, 6:05 AM · Catalog revision 5bc079fe355af2214bc0
Showing the snapshot bundled with this app (no content source is configured). Newer content may exist at the source.