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.
Этот ресурс доступен только на английском языке.
Промпты — это текст, который вы копируете в своего помощника. KitLocal их не запускает.
Заполните переменные
Всё, что вы вводите, остаётся в этом браузере. Это не добавляется в URL, не сохраняется и никуда не отправляется.
Предпросмотр
Ещё нужно: 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.
Назначение
Move from a wall of stack frames to a short list of testable hypotheses.
Когда использовать
- An exception appears and the cause is not obvious from the top frame.
- You want a disciplined checklist instead of guessing.
Что подготовить
- The full stack trace, including "Caused by" sections.
- What you were doing, what changed recently, and whether it is reproducible.
Ожидаемый результат
A numbered Markdown answer following the four sections above.
Об этом каталоге
Встроенный снимок · опубликовано 15 нояб. 2026 г., 06:05 · Ревизия каталога 5bc079fe355af2214bc0
Показан снимок, встроенный в приложение (источник контента не настроен). В источнике может быть более свежий контент.