StructuredFor DevelopersCode Writing & Debugging

Bug Diagnosis & Fix.

When you're stuck on a bug and need a systematic, explained fix rather than just a patch.

ChatGPT Β· Claude Β· GeminiΒ·IntermediateΒ·~900 tokens
Curated by the AIPP team
Last updated 14 May 2026 Β· v3
bug-diagnosis-fix-4.md Β· 900 words
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task.

# Context
- Pack: Developers & Tech Professionals
- Category: Code Writing & Debugging
- Use case: Bug Diagnosis & Fix
- Source task:
  - I have a bug in the following {{language}} code: {{code}}. The error message is: {{error_message}}. The expected behaviour is: {{describe}}. Diagnose:
  - 1. root cause of the bug
  - 2. why this error occurs
  - 3. the corrected code with the fix highlighted
  - 4. how to prevent this class of bug in future

# Goal
Root cause analysis, corrected code, and a prevention strategy for the same bug pattern.

# Constraints
- Produce a complete, usable first draft in one response.
- Avoid generic filler, vague advice, and unsupported claims.
- Make the output specific, practical, and ready to use.

# Output
Root cause analysis, corrected code, and a prevention strategy for the same bug pattern.

The variables to fill in

PlaceholderWhat to put thereExample
{{role}}Roledebugging expert
{{use_case}}Your specific valuebug diagnosis & fix
{{language}}LanguagePython
{{code}}Codepaste the function or component here
{{error_message}}Error messageTypeError: cannot read property id of undefined
{{describe}}Describereturn the user profile after login

How to customize this prompt

  1. Replace each {{double-curly}} with your real context.
  2. Adjust the constraints section to match your tone β€” formal, casual, blunt.
  3. If the engagement is recurring, change the duration line to mention milestones rather than days.
  4. Run it in your tool of choice. The output should be ready to paste with at most one small edit.

When to use

When you're stuck on a bug and need a systematic, explained fix rather than just a patch.

PRO TIP

Always paste the full error stack trace β€” the bug cause is almost always 3–5 lines up from the bottom of the trace.

Related prompts

Structured

Blog Post Drafting Engine

Write a complete, SEO-optimised blog post on the given topic. Include a compelling headline, an engaging introduction, 4-5 subheadings with detailed body paragraphs, and a strong conclusion with a cal

Structured

Email Newsletter Writer

Write a complete email newsletter including subject line, preview text, opening hook, main body content (3 short sections), and a clear call to action.

Structured

YouTube Video Script Writer

Write a complete YouTube video script including a strong hook (first 30 seconds), structured main content with transitions, and a closing that encourages likes, comments, and subscriptions.

Structured

LinkedIn Article Builder

Write a complete LinkedIn article that establishes professional authority, shares a genuine insight, and encourages professional discussion.

β˜… THIS PROMPT IS IN A PACK

The Developer Toolkit Pack

250 technical prompts for code review, documentation, architecture planning, debugging, test writing, API design, and career growth β€” built by developers for developers.

Browse more prompts β†’