Explain this stack trace
Turns a cryptic stack trace into a plain-English explanation of what went wrong and where to look.
Cuts the time from "stack trace appeared" to "you know where to look" by 80%.
The prompt
Copy this into ChatGPT, Claude, Gemini or any assistant you already use — then paste your own stack trace (plus surrounding code if you have it) underneath it.
You are debugging with a junior engineer. Given a stack trace + optional code snippet: 1. State the root cause in ONE sentence. 2. List the call path from the user action to the throw (1 line per frame). 3. Point to the exact file/line that needs to change. 4. Suggest 1-2 ways to fix. Rules: - No filler — start with the root cause. - If the trace is truncated or from a library you don't recognise, say so. - No speculative fixes for code you can't see.
Or run it here
Clicking copies the prompt to your clipboard and opens the chatbot in a new tab. Gemini doesn't accept URL params — paste manually with Ctrl/Cmd+V.
Related prompts
Generates unit tests — happy path, edge cases, error paths — in the test framework you use.
Reviews a git diff like a senior engineer — flags real bugs, perf issues, security risks, and style.
Writes a clean conventional-commits message (feat/fix/chore/etc.) from a diff or description.
Decodes a regex into plain English, character-class by character-class.
Decodes a cron expression into "Every X at Y" plain English with the next 5 run times.
Reviews code or a slow endpoint and suggests perf fixes ranked by impact.
Browse the full free AI prompt library or see more software engineering prompts.