Skip to main content
← Back to templates

Production Bug Investigator

Programming

Investigate a production bug down to its real root cause, not just a correlated symptom.

Role: You are a senior debugging engineer investigating a production bug.

Context: Code/system: [pasted the relevant service code]
Symptoms: intermittent 500 errors on the checkout endpoint, only under high concurrent traffic

Task: Step-by-step analysis, root cause, robust fix.

Constraints: Distinguish root cause from correlating symptoms; fix handles identified edge cases.

Output Format: Functionality -> problem -> root cause -> edge cases -> fix.

Expected output

A step-by-step analysis distinguishing the actual root cause (e.g. a race condition under concurrency) from symptoms that merely correlate with it, plus a robust fix that handles the identified edge cases, not just the reported symptom.

Usage tips

  • Describe the real symptoms precisely, including conditions (like "only under high concurrent traffic") — those details are what point toward the real root cause, not a guess.
  • Test the fix specifically against the conditions that triggered the original bug, not just a normal-path smoke test.

Try it

Fill in the placeholders below and see the compiled prompt update live.

The code to work with.

What you're observing.

48
Words
358
Characters
0/2
Placeholders filled
1 min
Reading time
Quality score11
  • Completeness0
  • Clarity0
  • Context0
  • Specificity0
  • Constraints0
  • Format0
  • Output0
  • Constraints note100
  • Success criteria0
  • Scope focus100
  • Verification step0
  • Negative example0
  • Confidence0
  • Placeholder syntax100
  • Markdown structure0
Suggestions
  • Fill in the remaining placeholders.
  • Expand your answers — a few words each isn't enough detail for the model to work with.
  • Add background context so the model understands the situation.
Role: You are a senior debugging engineer investigating a production bug. Context: Code/system: {{CODE}} Symptoms: {{SYMPTOMS}} Task: Step-by-step analysis, root cause, robust fix. Constraints: Distinguish root cause from correlating symptoms; fix handles identified edge cases. Output Format: Functionality -> problem -> root cause -> edge cases -> fix.
AI Assistant

Jump to a page…

Navigation