PL-07 Sample v1.0 · updated 4 Jul 2026
Explain an error message and what to check first
Turns a stack trace or error into a plain explanation, the most likely causes in order, and one quick check for each.
- Task
- Code
- Level
- Practitioner
- Placeholders
- 3
- Works with
- Chat, Reasoning, Local
I got this error while using {{tool}}.
What I was doing: {{context}}
Error:
```
{{error}}
```
Please:
1. Explain in plain language what the error means.
2. List the three most likely causes, most likely first, and say why you ranked them that way.
3. For each cause, give one quick check I can run to confirm or rule it out.
4. Only then suggest a fix for the most likely cause.
If the error could have a cause you cannot judge from this information, tell me what else to send you.
Words in double braces are placeholders. Replace them before you send the prompt, here or in your tool.
Fill in the prompt
Filling in on the page needs JavaScript. Copy the prompt by selecting it, then replace each placeholder in your tool.
| Placeholder | What to put there | Example |
|---|---|---|
{{tool}} | Language, tool or library. With versions if you know them. | Node.js 22 with a PostgreSQL client library |
{{context}} | What you were doing. The command you ran or the action you took. | running the database migration on my laptop for the first time |
{{error}} | The error. The full message and stack trace. Remove secrets, hostnames and personal data. | (paste the error here) |
Is it the right prompt?
Use it when
- An error message makes no sense to you yet.
- You want to know where to look before you start changing code.
Skip it when
- The log contains customer data or secrets you cannot remove.
- You want the model to make changes directly in a production system.
How to adapt it
- It worked yesterday
- Add what changed since then: updates, configuration, data.
- You are learning the language
- Ask it to explain each line of the stack trace.
Check the answer
Before you rely on the result, confirm that:
- The causes are ranked with a reason, not just listed.
- Each check is something you can run without changing code.
- The suggested fix addresses the cause you confirmed, not a different one.
Watch out for
- Security Error logs often include tokens, hostnames and file paths. Remove them before pasting.
- Accuracy Run the checks before applying a fix; the first explanation is not always the right one.
Revision history
| Version | Date | Change |
|---|---|---|
| v1.0 | First sample version. |