When you paste a stack trace and ask an AI to fix it, it usually patches wherever the error surfaces not where the bug originates. I built a prompt that forces the model to work the problem in order: read the symptom literally, rank hypotheses by likelihood with confidence levels, identify the actual origin (not just the throw site), then propose a fix and a way to verify you actually found the root cause not just made the error move.t: instantly share code, notes, and snippets.
No reviews yetBe the first to leave a review for AI Bug Triage Prompt
Framer AI AgentsDesign and publish professional sites with AI
Promoted
Maker
📌
This started from a frustration I kept running into: paste a stack trace into an AI assistant, get a fix, apply it, and the error moves somewhere else. Repeat until you've wasted an afternoon.
The problem isn't the model it's that "fix this bug" is the wrong prompt. It skips straight to a solution before anything is actually understood. The crash site and the bug origin are often two completely different places, and a patch at the throw site just hides the symptom.
So I built prompts that enforce an order diagnosis before fix, ranked hypotheses before commitment, and a verification step so "the error went away" isn't mistaken for "I found the cause." Six prompts in total covering the full lifecycle: code review, bug triage, refactor planning, test generation, PR descriptions, and incident postmortems.
The bug triage prompt is free here: https://gist.github.com/chatterj...
Happy to answer any questions about how any of the prompts are structured or what I was trying to solve with each one.