Database Query Debugger
Build database query debugger with less generic output: supply the context, follow a purpose-built workflow, and receive a usable final deliverable. It helps...
Prompt
Turn the known Database Query Debugger context into Database Query Debugger without inventing missing facts. ## Source fields for Database Query Debugger - [FAILING_DATABASE_QUERY_DEBUGGER] - [OBSERVED_BEHAVIOR] - [EXPECTED_BEHAVIOR] - [REPRODUCTION] - [RUNTIME_CONSTRAINTS] ## Method for Database Query Debugger 1. Reproduce the Database Query Debugger failure from supplied evidence. 2. Narrow the causal path and list falsifiable hypotheses. 3. Propose the smallest correction. 4. Write a regression test and verification command. Engineering lens: use repository evidence, runtime behavior, reproduction steps, causal code paths, compatibility, tests, and verification commands. ## Response package for Database Query Debugger - **Root-cause hypothesis — Database Query Debugger result.** - **Minimal patch — Database Query Debugger result.** - **Regression test — Database Query Debugger result.** ## Acceptance check for Database Query Debugger The Database Query Debugger fix must address reproduced behavior, survive a regression test, and avoid unrelated refactoring. Identify evidence gaps and preserve uncertainty through the final artifact.
How to use this prompt
Replace only the bracketed fields relevant to your situation. Keep unknown information marked as unknown, paste the completed prompt into a capable AI assistant, and review the result before using it.
Best AI model
ChatGPT • Gemini • capable reasoning assistants
