Task prompt · Coding
Find and fix a bug from an error message
by Agent Yard TeamPaste the error and get the root cause, not a guess.
Use cases
- Paste the error and get the root cause, not a guess.
- When you already have a screenshot or a file and want the AI to work from it instead of starting from scratch.
- Reuse it as often as you like: fill in the blanks (paste error and stack trace or attach screenshot; steps; expected) with new details and copy again.
- As one step of the Build an app with AI prompt pack.
Featured in: Best Claude prompts for coding, Best Claude prompts for code review and debugging, Best AI prompts for debugging and bug reports.
How to use it
- Open Cursor or Claude Code in your terminal (or another AI listed here).
- Attach the screenshot (or paste it straight into the chat).
- Attach the file (PDF, Word, CSV or Excel), or paste its text into the prompt.
- Fill in the highlighted blanks ([PASTE ERROR AND STACK TRACE OR ATTACH SCREENSHOT], [STEPS], [EXPECTED]…) below, or edit them after pasting.
- Copy the prompt, paste it into the chat and send.
Fill in the blanks (optional)
Prompt
I'm getting this error: [PASTE ERROR AND STACK TRACE OR ATTACH SCREENSHOT]. What I was doing when it happened: [STEPS]. Expected: [EXPECTED]. Actual: [ACTUAL]. Find the root cause before proposing a fix. Walk through the stack trace, name the most likely cause and two alternatives, and say what evidence would confirm each. Then give the smallest fix, explain why it works, and add a test that would have caught it.
One email a week
The Weekly is presented byyour brandSponsored · openThe best new prompts and personas, nothing else.