In the pack: ChatGPT, Claude & Gemini Prompts for Coding and Developers
Hypothesis-Driven Debugging for a Bug You Can't Explain
Prompt
System and stack: {{FRAMEWORK}}
Symptom (expected vs actual, exact messages, how often): {{SYMPTOM}}
What I've already tried and what happened each time: {{ALREADY_TRIED}}
What changed recently (deploys, dependencies, config, data, traffic): {{RECENT_CHANGES}}
Relevant code or logs: {{EVIDENCE}}
Do this:
1. Restate the bug as a precise, testable statement.
2. List five or more hypotheses across different layers (code, data, config, environment, concurrency, dependencies). For each, say what it predicts I would observe.
3. Use my "already tried" results to strike out hypotheses they've ruled out, and say why.
4. Rank the rest by likelihood × cheapness to test.
5. For the top three, design one experiment each: the exact change or command, and the result that would confirm it versus kill it.
6. Tell me what to log or capture before the next occurrence if the bug is intermittent.
Don't propose a fix yet. I'll come back with results and we'll iterate.
Customize this prompt
Fill in the variables below to personalize this prompt:
Model Settings
Recommended Models
Temperature
Max Tokens
Additional Notes
About this prompt
“Hypothesis-Driven Debugging for a Bug You Can't Explain” is a free prompt for ChatGPT in the Coding & Software category, 179 words long, added to The Prompt Index on October 28, 2026 by The Prompt Index. Copy it with the button above, paste it into ChatGPT or any other AI chat assistant, and send it.
It has 5 placeholders to fill in first:
{{FRAMEWORK}}, {{SYMPTOM}}, {{ALREADY_TRIED}}, {{RECENT_CHANGES}}, {{EVIDENCE}}.
Use the “Customize this prompt” fields to personalise it before you copy.
Recommended models: ChatGPT, Claude, Gemini.
0 upvotes, sent to an AI tool 0 times, viewed 4 times.
Browse all Coding & Software prompts, the AI prompt database or use the AI prompt finder to search every prompt.