AI Prompt for Fixing Runtime Errors

Copy-paste AI prompt for fixing runtime errors: paste your stack trace and code to get ranked causes, a working fix, and prevention tips in minutes.

The prompt

Role: You are a senior software engineer with 10+ years of experience debugging [LANGUAGE] applications in production.

Context: I am getting a runtime error in my [LANGUAGE] project. The project uses [FRAMEWORK_OR_LIBRARIES]. My experience level is [BEGINNER/INTERMEDIATE/ADVANCED].

Error message and stack trace:
[ERROR_MESSAGE_AND_STACK_TRACE]

Relevant code:
[CODE_SNIPPET]

What I was trying to do:
[WHAT_YOU_WERE_TRYING_TO_DO]

Task: 1) Explain in plain language what this error means and why it happens. 2) List the 3 most likely root causes, ranked by probability, with a one-line reason for each. 3) Provide the corrected code with the smallest possible change, keeping my existing style. 4) Explain exactly what you changed and why. 5) Suggest how to prevent this class of error in the future.

Format: Use clear headings for each of the 5 sections. Put all code in fenced code blocks with the language tag. Keep explanations jargon-free enough for a [BEGINNER/INTERMEDIATE/ADVANCED] developer.

Constraints: Do not rewrite my entire file — only fix what is broken. Do not suggest switching languages or frameworks. If you need more information to be certain, ask me one focused question before giving the fix.

Variables to fill in

Replace each [variable] in the prompt with your own details:

[LANGUAGE] [FRAMEWORK_OR_LIBRARIES] [BEGINNER/INTERMEDIATE/ADVANCED] [ERROR_MESSAGE_AND_STACK_TRACE] [CODE_SNIPPET] [WHAT_YOU_WERE_TRYING_TO_DO]

Example input

LANGUAGE=Python, FRAMEWORK_OR_LIBRARIES=Django 4.2, level=BEGINNER, error=TypeError: 'NoneType' object is not subscriptable at views.py line 42, trying to read a query param that may be missing

How to use this prompt

Paste the full stack trace — never paraphrase it, since exact line numbers and error types matter. Include the smallest code snippet that reproduces the error, plus one sentence about what you expected to happen.

Tips for the best results

If the first fix does not work, reply with the new error message instead of starting over — the AI keeps the context.
Ask it to explain the error in one sentence first if the full answer is too long to scan quickly.
For recurring errors, save the prevention tip as a snippet or linter rule in your project.

Frequently asked questions

Should I paste my entire file into the prompt?

No. Paste the smallest snippet that still reproduces the error, plus the full stack trace. Huge files dilute the AI's focus and can hit token limits.

What if the AI's fix is wrong?

Reply with the exact new error or unexpected behavior. Iterative debugging with full error text converges much faster than rephrasing your original question.

Related SlickCalcs tools

Scientific Calculator

More coding prompts

AI Prompt for SQL-to-ORM Conversion

Convert raw SQL to ORM code with this AI prompt: idiomatic queries for your ORM, N+1 risks flagged, and guidance on what should stay raw SQL.

AI Prompt for Storage Decisions

Decide where data lives with this AI prompt: database vs cache vs memory analysis on durability, latency, size, and operational cost trade-offs.

AI Prompt for Structure Trade-offs

Compare data structures head-to-head with this AI prompt: trade-off matrix on your workload, cache and memory analysis, and a conditional winner.

AI Prompt for Sync-to-Async Conversion

Convert sync code to async with this AI prompt: correct async/await conversion, independent calls parallelized, and every semantic change flagged.

AI Prompt for Git Commit Messages

Write perfect git commit messages with this AI prompt: conventional-commit format from your diff, with the why explained and scope chosen correctly.

AI Prompt for REST-to-GraphQL

Convert REST to GraphQL with this AI prompt: client-driven schema design, N+1-safe resolvers with batching, and a reversible strangler migration plan.