Bisect a regression
Model notes: Any model
Fill in the variables (optional — they're inserted live below):
Something broke between {{good_version}} and {{bad_version}}. Symptom: {{symptom}}.
Walk me through using `git bisect` to find the commit: the exact commands, how to write an automated test script for `git bisect run` for this symptom, and what to do when I find the commit (how to read it, revert vs fix-forward).
How to use it
- Fill the variables above, or replace each
{{variable}}after pasting. - Paste into your AI tool (ChatGPT, Claude, Gemini, Cursor, Claude Code, or a local model in Ollama/LM Studio).
- Review the output. Models make mistakes, especially with facts, numbers and code.
Get all 209 prompts + agent workflows
Every prompt as Markdown and JSON, 10 multi-step agent workflows, and 12 ready-made slash commands for Cursor and Claude Code. Instant zip download, one-time purchase.
More Debugging prompts
Debugging
Root-cause a bug, don't patch symptoms
Strong reasoning model recommended
Variables: expectedactualstepserror_outputcode_or_files
Help me find the root cause of this bug. Don't propose a fix until we've confirmed the cause.
What I expected: {{expected}}
What happened: {{actual}}
Steps to reproduce: {{steps}}
Error / logs:
```
{{error_output}}
```
Relevant code: {{code_or_files}}
Process:
1. List 3-5 plausible hypotheses, ranked by likelihood, each with the evidence for and against.
2. For the top hypothesis, give me the single quickest experiment (log line, breakpoint, command) to confirm or rule it out.
3. Wait for my result before continuing. Help me find the root cause of this bug. Don't propose a fix until we've confirmed the cause.
What I expected: {{expected}}
What happened: {{actual}}
Steps to reproduce: {{steps}}
Error / logs:
```
{{error_output}}
```
Relevant code: {{code_or_files}}
Process:
1. List 3-5 plausible hypotheses, ranked by likelihood, each with the evidence for and against.
2. For the top hypothesis, give me the single quickest experiment (log line, breakpoint, command) to confirm or rule it out.
3. Wait for my result before continuing.
Open & fill variables → Debugging
Explain this error like I'm new to the stack
Fine on small local models (7B+)
Variables: error_messagelanguage_or_framework
Explain this error message in plain English:
```
{{error_message}}
```
Context: I'm using {{language_or_framework}}.
Tell me: what it literally means, the 3 most common causes, how to check which one applies to me, and the usual fix for each. Keep it under 250 words. Explain this error message in plain English:
```
{{error_message}}
```
Context: I'm using {{language_or_framework}}.
Tell me: what it literally means, the 3 most common causes, how to check which one applies to me, and the usual fix for each. Keep it under 250 words.
Open & fill variables → Debugging
Stack trace triage
Paste the full trace, not a screenshot
Variables: languagestack_trace
Here is a stack trace from {{language}}:
```
{{stack_trace}}
```
1. Identify the frame where the error originates in MY code (not library code) and explain why that's the likely culprit.
2. Explain the chain of calls that led there.
3. List what information is missing to be sure (variable values, inputs).
4. Suggest the exact log statements to add, with file and line, to capture that information. Here is a stack trace from {{language}}:
```
{{stack_trace}}
```
1. Identify the frame where the error originates in MY code (not library code) and explain why that's the likely culprit.
2. Explain the chain of calls that led there.
3. List what information is missing to be sure (variable values, inputs).
4. Suggest the exact log statements to add, with file and line, to capture that information.
Open & fill variables → New prompts every week
One short email with the best new prompts and agent workflows we've tested. Free; unsubscribe any time.