Code review & debugging21 categories

Rubber duck, but it asks questions

Stuck, and not yet sure what you're even stuck on.

I am stuck on a bug. Do not suggest fixes yet.

Ask me questions, one at a time, to narrow down where the problem is. After each answer, tell me what it rules in or out before asking the next.

Start with the broadest split you can: is this a problem of wrong data going in, wrong logic in the middle, or wrong handling of the result? Then keep halving.

Only once you're confident you've located it should you propose a cause. Then ask me to verify before suggesting a fix.

Here is what I know so far:

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.Read this stack trace with meAn error you haven't seen before, with a trace that isn't obviously pointing anywhere.Find why this is slowSomething is sluggish and you don't yet know what to measure.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