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.
Cette ressource n’est disponible qu’en anglais.
Les prompts sont du texte que vous copiez dans votre propre assistant. KitLocal ne les exécute pas.
Renseigner les variables
Ce que vous saisissez reste dans ce navigateur. Cela n’est ni ajouté à l’URL, ni enregistré, ni envoyé.
Aperçu
Encore requis : 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.
Objectif
Move from a wall of stack frames to a short list of testable hypotheses.
Quand l’utiliser
- An exception appears and the cause is not obvious from the top frame.
- You want a disciplined checklist instead of guessing.
Ce qu’il faut préparer
- The full stack trace, including "Caused by" sections.
- What you were doing, what changed recently, and whether it is reproducible.
Résultat attendu
A numbered Markdown answer following the four sections above.
À propos de ce catalogue
Instantané intégré · publié 15 nov. 2026, 06:05 · Révision du catalogue 5bc079fe355af2214bc0
Affichage de l’instantané intégré à l’application (aucune source de contenu n’est configurée). Du contenu plus récent peut exister à la source.