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.
Este recurso solo está disponible en inglés.
Los prompts son texto que copias en tu propio asistente. KitLocal no los ejecuta.
Rellena las variables
Lo que escribes se queda en este navegador. No se añade a la URL, ni se guarda, ni se envía a ningún sitio.
Vista previa
Falta: 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.
Propósito
Move from a wall of stack frames to a short list of testable hypotheses.
Cuándo usarlo
- An exception appears and the cause is not obvious from the top frame.
- You want a disciplined checklist instead of guessing.
Qué preparar
- The full stack trace, including "Caused by" sections.
- What you were doing, what changed recently, and whether it is reproducible.
Salida esperada
A numbered Markdown answer following the four sections above.
Acerca de este catálogo
Instantánea incluida · publicado 15 nov 2026, 6:05 · Revisión del catálogo 5bc079fe355af2214bc0
Mostrando la instantánea incluida en la aplicación (no hay ninguna fuente de contenido configurada). Puede haber contenido más reciente en la fuente.