Explain a compiler or interpreter error message in plain English, naming the error type, likely cause, how to read the stack trace, and relevant frame.
You are a teaching assistant who has watched panic set in the moment a wall of red text appears in a terminal, and your first move is always the same, slow down, read what the error is actually a name for, and only then start hunting for the specific cause, because most of that wall of text is far less frightening once it has a plain-English label attached to it. My error message is: [ERROR_MESSAGE] My code that produced it, if I have it available to share, is: [CODE?] If I left [ERROR_MESSAGE] blank, ask me to paste the actual error before doing anything else instead of guessing at a generic one. Identify the programming language from the format of the error itself, a Python traceback, a JavaScript stack trace, a Java exception, or a C or C++ compiler error all look distinct, and name which one you are reading. First, name the specific error type, such as `NameError`, `TypeError`, `SyntaxError`, `IndexError`, `undefined is not a function`, `NullPointerException`, `ReferenceError`, or a segmentation fault, and explain in plain language what that category of error means in general, before looking at my specific situation at all. If the error includes a stack trace with multiple frames, explain how to read it, note whether the language convention is to read the trace top to bottom or bottom to top to find where the error actually originated, and identify which frame in the trace is likely my own code versus internal library or language runtime code, since the frame worth focusing on is almost always the deepest one that is still inside code I wrote. If I provided [CODE], point to the specific line or pattern most likely responsible for this exact error, and explain concretely what the computer was trying to do when it hit this problem. If I did not provide code, give me a short checklist of the two or three most common causes of this specific error type, phrased as questions I can check against my own code, such as whether a variable was spelled consistently everywhere it is used, or whether an index could be running past the end of a list. Close by explaining, in one or two sentences, a habit or a small check that would have caught this specific class of error earlier, so the value here is not just fixing this one error but recognizing its shape faster the next time it shows up.
Use this prompt anywhere
10,000+ expert prompts for ChatGPT, Claude, Gemini, and wherever you use AI.
Get Early AccessA wall of red terminal text is intimidating mostly because it looks like one undifferentiated block. Almost every error message actually has a name, TypeError, NullPointerException, segmentation fault, and once that name has a plain-English meaning attached, the rest of the trace stops being noise and starts being a map.
This tool reads your [ERROR_MESSAGE] first for its category, explaining what that type of error generally means before looking at your specific situation. If it includes a stack trace, it explains how to read it, whether the convention for your language is top to bottom or bottom to top, and which frame is actually your code versus internal library or runtime code, the one worth focusing on and the one most beginners skip past.
Add your [CODE] if you have it and the explanation points to the specific line or pattern most likely responsible, describing concretely what the computer was doing when it hit the problem. Without code, you get a short checklist of the most common causes for that error type, phrased as questions to check against your own work. Every explanation closes with the habit that would have caught this class of error sooner, so the value isn't just this one fix, it's recognizing the same shape faster next time. Run it in the Dock Editor for a log of explained errors, pair with the find the bug challenge to find the line, or the debugging practice generator to practice on generated bugs first.
Drop the full error or stack trace into [ERROR_MESSAGE]. The tool identifies the language and error type from its format and asks for a real error if you leave it blank.
Share the code that produced the error in [CODE] for a specific pointer to the likely line, or skip it for a general checklist of common causes instead.
Before anything specific to your case, the error's category, like TypeError or NullPointerException, gets explained in plain language on its own.
If your error includes a trace, get told which direction to read it in for your language and which frame is your own code versus internal library code.
Every explanation ends with a small check or habit that would catch this specific class of error earlier next time, not just a fix for this one instance.
Paste an intimidating wall of red terminal text and get it broken into a named error type, a plain explanation of what that means, and which line in the trace actually matters.
Working alone on an assignment at night with an error you don't recognize, get a plain-English explanation and a checklist of common causes instead of waiting for office hours.
Build the skill of identifying which stack trace frame is your own code versus library internals, the single habit that speeds up debugging the most once it clicks.
Python tracebacks, JavaScript stack traces, and Java exceptions all format differently. Get the reading convention for whichever language's error you're actually facing.
Discover more prompts that could help with your workflow.
Build a small working program that calls a real public API, with the request, response, and API key setup explained step by step.
Explain a core functional programming idea, such as pure functions or immutability, with a broken code example and its fixed version shown side by side.
Explain a built-in math function, square root, power, absolute value, or rounding, covering math and syntax, then generate practice calls to predict before revealing results.
10,000+ expert-curated prompts for ChatGPT, Claude, Gemini, and wherever you use AI. Our extension helps any prompt deliver better results.