AI Prompts for Claude for Debugging

I am getting this error: [PASTE FULL ERROR MESSAGE AND STACK TRACE]. Here is the code that triggers it: [PASTE CODE]. What is the root cause and how do I fix it?

This error message is confusing: [PASTE ERROR]. Break it down for me. What is it actually saying, where is it coming from, and what class of problem does it represent?

I have a crash that only happens in production, not locally. Here is the stack trace: [PASTE]. Here are the differences between my environments: [LIST DIFFERENCES]. What should I investigate?

I am getting [ERROR TYPE] from [LIBRARY/FRAMEWORK]. Here is the context: [PASTE CODE AND CONFIG]. Is this a bug in my code, a misconfiguration, or a known issue with the library?

Walk me through reading this stack trace: [PASTE TRACE]. What does each frame mean, where did execution start, and where did it fail?

My code runs without errors but produces wrong output. Input: [EXAMPLE]. Expected output: [EXPECTED]. Actual output: [ACTUAL]. Here is the code: [PASTE]. Walk through what it is actually doing.

This function returns [WRONG VALUE] when I pass [INPUT]. I expect [CORRECT VALUE]. Trace through the logic and tell me where it goes wrong: [PASTE CODE].

I have a race condition or intermittent bug. It happens about [FREQUENCY] and I cannot reproduce it reliably. Here is the relevant code: [PASTE]. What are the most likely causes?

This code works for most inputs but fails on [SPECIFIC CASE]. Here is the code: [PASTE]. Why does this edge case break it, and what is the fix?

My state is getting corrupted somewhere. After running [SEQUENCE OF OPERATIONS], the state is [WRONG STATE] when it should be [CORRECT STATE]. Here is the relevant code: [PASTE]. Where is the mutation happening?

I have been debugging [PROBLEM] for [TIME] and I am stuck. Here is what I know: [DESCRIBE]. Here is what I have tried: [LIST]. What should I try next? What am I probably missing?

Help me build a debugging strategy for this problem: [DESCRIBE BUG]. What hypotheses should I test first, what would confirm or eliminate each one, and what is the most efficient order to check?

I need to add logging to find this bug: [PASTE CODE]. Where should I add log statements, and what should I log to efficiently narrow down the problem?

I want to write a minimal reproduction of this bug. The full codebase is complex but the bug seems related to [AREA]. Help me isolate the smallest possible reproduction case.

I fixed what I thought was the bug but the problem persists. Original bug: [DESCRIPTION]. Fix I applied: [PASTE FIX]. New symptom: [DESCRIBE]. Is the original bug actually fixed, or did I fix the wrong thing?

I just fixed this bug: [DESCRIBE BUG AND FIX]. Write a regression test that would have caught it. Include the test setup, the assertion, and any edge cases that test the same failure mode.

This class of bug (e.g., null pointer, off-by-one, type coercion) keeps appearing in my codebase. What patterns or linting rules would prevent it systematically?

After this debugging session, what should I add to my codebase to make this type of bug easier to catch in the future? [DESCRIBE THE BUG AND FIX].

Review this fix and tell me if it introduces new problems: [PASTE ORIGINAL BUG]. Fix: [PASTE FIX]. Is this the right fix, or does it just move the problem somewhere else?

I want to add assertions or invariant checks to catch this kind of bug earlier: [PASTE CODE]. Where should I add defensive checks, and what should they verify?