メインコンテンツへスキップ
kitlocal.dev

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.

このカタログについて

同梱スナップショット · 2026/11/15 6:05 に公開 · カタログのリビジョン 5bc079fe355af2214bc0

アプリに同梱されたスナップショットを表示しています(コンテンツソースが設定されていません)。ソース側にはより新しいコンテンツがある可能性があります。