Debugging prompts

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.

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.

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.

My app works locally but fails in {{environment}}.

Symptom: {{symptom}}
Local setup: {{local_setup}}
Production setup: {{prod_setup}}
Logs from production: {{logs}}

Walk through the usual local-vs-prod differences one by one (env vars, build mode, file paths and case sensitivity, network/CORS, timeouts, memory, dependency versions, time zones, permissions, caching/CDN) and for each say whether it fits my symptom and how to check it. Finish with the top 3 suspects.

My app works locally but fails in {{environment}}. Symptom: {{symptom}} Local setup: {{local_setup}} Production setup: {{prod_setup}} Logs from production: {{logs}} Walk through the usual local-vs-prod differences one by one (env vars, build mode, file paths and case sensitivity, network/CORS, timeouts, memory, dependency versions, time zones, permissions, caching/CDN) and for each say whether it fits my symptom and how to check it. Finish with the top 3 suspects.

This test passes sometimes and fails sometimes:

```
{{test_code}}
```
Failure output: {{failure_output}}

List the likely sources of flakiness in this specific test (timing/async, shared state, test order, randomness, dates/time zones, network, unseeded data). For each, point to the exact line that makes it vulnerable and show a deterministic rewrite.

This test passes sometimes and fails sometimes: ``` {{test_code}} ``` Failure output: {{failure_output}} List the likely sources of flakiness in this specific test (timing/async, shared state, test order, randomness, dates/time zones, network, unseeded data). For each, point to the exact line that makes it vulnerable and show a deterministic rewrite.

This is slow: {{what_is_slow}} (currently ~{{current_time}}, target {{target_time}}).

Code / query:
```
{{code}}
```

1. Point out the likely hotspots and estimate their cost (big-O or I/O round trips).
2. Tell me how to measure before changing anything (profiler, EXPLAIN, timing logs) for {{stack}}.
3. Suggest fixes in order of effort vs impact. Don't sacrifice readability for micro-optimisations.

This is slow: {{what_is_slow}} (currently ~{{current_time}}, target {{target_time}}). Code / query: ``` {{code}} ``` 1. Point out the likely hotspots and estimate their cost (big-O or I/O round trips). 2. Tell me how to measure before changing anything (profiler, EXPLAIN, timing logs) for {{stack}}. 3. Suggest fixes in order of effort vs impact. Don't sacrifice readability for micro-optimisations.

Be my rubber duck. I'll explain what my code is supposed to do, line by line. Your job:
- Ask one short clarifying question at a time.
- Point out any place where what I say and what the code does don't match.
- Don't give me the answer unless I ask "just tell me".

Here's the code and my explanation:
{{code_and_explanation}}

Be my rubber duck. I'll explain what my code is supposed to do, line by line. Your job: - Ask one short clarifying question at a time. - Point out any place where what I say and what the code does don't match. - Don't give me the answer unless I ask "just tell me". Here's the code and my explanation: {{code_and_explanation}}

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).

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).