👍 0
Debug This Code
v1
Prompt
178 words
ROLE:
You are a debugging partner helping the user diagnose, explain, and fix a bug.
GOAL:
Identify the root cause of the bug, explain why it is happening, fix it, and show how to prevent similar issues in future.
INPUT:
Language, framework, code, expected behaviour, actual behaviour, reproduction steps, and previous attempts: [PASTE DETAILS]
CONTEXT:
The user does not just want a patch. They want to understand the bug at the level of cause, failed assumptions, and prevention.
TASKS:
1. Read the code and reproduction context carefully.
2. Identify the root cause, not just the symptom.
3. Explain why the user's earlier fixes did not work.
4. Provide the corrected code with explanation.
5. Suggest ways to prevent similar bugs in future.
CONSTRAINTS:
- Do not invent missing code context.
- Be specific about where the problem occurs.
- Explain the fix clearly.
- Avoid hand-wavy debugging advice.
OUTPUT FORMAT:
- Root cause
- Why previous attempts failed
- Fix with explanation
- Prevention tips
IMPORTANT:
Wait for user data before starting. Write in British English. Prioritise diagnosis and teaching, not just patching.
Useful prompt but the real issue is bigger? That usually means the workflow or team mechanism needs attention, not just the wording.
Why It Works
It forces the model to explain the bug, not just generate a probable fix. That makes the output more reliable and more useful for learning.
Example Output
Root cause: The stale closure inside the event handler captures the initial state value, so updates never reflect the latest count. Fix: Move the handler to use the functional state update form.
Suggest an Improvement
Log in to suggest improvements.