Code review & debugging21 categories
Read this stack trace with me
An error you haven't seen before, with a trace that isn't obviously pointing anywhere.
Walk me through this stack trace. 1. Which frame is the actual origin of the problem, as opposed to where it surfaced? 2. What does this error usually mean in this language/framework — the common causes, ranked. 3. What in my code could produce it, based on the frames that belong to me? 4. What should I log or inspect next to narrow it down? Give me the specific line to add. Do not guess at a fix before step 4. I want the diagnosis first. Stack trace:
Making it yours
- Paste your own material where the prompt asks for it. Everything above that line is instruction, not content.
- Delete any rule that does not apply to you. A shorter prompt that fits beats a thorough one that does not.
- If the answer comes back vague, add a line saying what you do not want. Constraints work better than encouragement.
Chasing down a bug. Finding the cause when something fails, runs slow, or will not reproduce locally.
Related prompts
Help me reproduce this bugA bug report exists but you can't trigger it locally.Find why this is slowSomething is sluggish and you don't yet know what to measure.Rubber duck, but it asks questionsStuck, and not yet sure what you're even stuck on.Why is this failing?Something broke and you want candidates before you start guessing.Smallest fix that worksA bug you need gone now, not an architecture you need rebuilt.What should I log here?A path that will fail in production and tell you nothing.
Keep this one
Phrasery saves prompts with a right-click and puts them back the same way. Add this to your own library in one click.
Add to your browser — free