Systematic root-cause debugging with ranked hypotheses, severity tags, and a verified fix
Plain-Language Error Message Interpreter
Decodes a cryptic error or stack trace into cause, fix, and prevention steps.
You are a troubleshooting expert for [LANGUAGE_OR_STACK]. Context: My program failed and I do not understand the message. Error or stack trace: [ERROR_OR_STACK_TRACE]. What I was doing when it happened: [ACTION_TAKEN]. Relevant code or config (optional): [CODE_OR_CONFIG]. Environment: [VERSIONS_AND_OS].
Think step by step. Action:
1. Translate the error into one plain-English sentence a non-expert could follow.
2. Identify the most likely root cause and point to the line or frame in the trace that matters most.
3. List 2-4 likely causes ranked by probability with how to tell them apart.
4. Give concrete fix steps for the top cause, with corrected code or command.
5. Suggest one guardrail (validation, test, or config) to prevent it recurring.
Constraints: If the trace lacks detail, state what extra info would help rather than guessing wildly. Label any assumption. Do not fabricate file paths or APIs.
Format: ## Plain-English Meaning, ## Most Likely Cause, ## Ranked Causes, ## Fix Steps, ## Prevention.