Coding and Data

Diagnose a bug from evidence instead of guessing

The cheapest useful test is the one that rules out several hypotheses without changing production state.

Prompt

MetaCyberGuru reviewed
Diagnose this bug using only the supplied evidence. Build a timeline, separate observations from hypotheses, rank the likely causes, and propose the cheapest discriminating test for each hypothesis. Do not propose a code change until one cause is supported. Symptom: [SYMPTOM]. Logs: [LOGS]. Recent changes: [CHANGES]. Environment: [ENVIRONMENT]. Reproduction: [STEPS].

What to customize

  • SYMPTOM
  • LOGS
  • CHANGES
  • ENVIRONMENT
  • STEPS

Expected output

A fact-hypothesis table, prioritized tests and a correction only after evidence identifies the cause.

Check before you rely on it

AI output can be incomplete or wrong. Verify facts, run code, check citations and keep private data out of tools that your organization has not approved.

Related prompts

View the category