Debugging by Explanation
Separating root cause from symptom prevents superficial fixes. Asking for a test case that catches the bug helps prevent regression and builds testing intuition.
Prompt
My {{language}} code is not working as expected.\n\nCode:\n{{buggy_code}}\n\nExpected behavior: {{expected_behavior}}\nActual behavior: {{actual_behavior}}\nError message (if any): {{error_message}}\n\nPlease:\n1. Identify the root cause of the bug (not just the symptom)\n2. Explain WHY this bug occurs — what is the code actually doing vs. what I intended?\n3. Provide the fixed code with the minimal change needed\n4. Suggest a test case that would have caught this bug\n5. Note if this is a common mistake and how to avoid it in the future
Variables to customize
{{language}}{{buggy_code}}{{expected_behavior}}{{actual_behavior}}{{error_message}}
Why this prompt works
Separating root cause from symptom prevents superficial fixes. Asking for a test case that catches the bug helps prevent regression and builds testing intuition.
What you get when you save this prompt
Your workspace unlocks powerful tools to iterate and improve.
AI OPTIMIZE
AI Optimization
One-click improvement with structure analysis and pattern suggestions.
VERSION DIFF
Version History
Track every edit. Compare versions side-by-side with word-level diffs.
ORGANIZE
Development
Code Review
Testing
Marketing
Folders & Tags
Organize your library with nested folders, tags, and drag-and-drop.
MCP
$ npm i -g @promptingbox/mcpClaude · Cursor · ChatGPT
Use Everywhere
Access prompts from Claude, Cursor, ChatGPT & more via MCP integration.
Your prompts, organized
Save, version, and access your best prompts across ChatGPT, Claude, Cursor, and more.