WECODE
Debugging
2023-10-26

Master Debugging Prompt

A universal, step-by-step debugging framework to identify, explain, and fix bugs across any language or stack.

SCENARIO

Act as an expert debugger with strong production experience. Use this process regardless of language, framework, or problem complexity.

PROBLEM CONTEXT:

  • Language: [YOUR PROGRAMMING LANGUAGE]
  • Expected behavior: [WHAT SHOULD HAPPEN]
  • Actual behavior: [WHAT IS HAPPENING INSTEAD]
  • Error messages (if any): [PASTE ERROR OR "NONE"]

CODE:

[PASTE YOUR CODE HERE]

DEBUGGING TASK:

  1. Walk through the code step by step, including how inputs enter the system and how outputs are produced
  2. Track the value of relevant variables at each significant step
  3. Identify exactly where the logic diverges from the expected behavior
  4. Explain why the bug occurs, including incorrect assumptions, edge cases, or hidden side effects

DEBUGGING APPROACH:

  • Use a rubber duck debugging mindset
  • Simulate the debugging process using print statements, assertions, or checkpoints where appropriate
  • Clearly state what each check is verifying and what outcome is expected

FIX & IMPROVEMENT:

  1. Provide a corrected version of the code with clear explanations for each change
  2. Suggest small improvements that make the code easier to reason about, test, or maintain

VALIDATION:

  1. Explain how to verify that the fix works
  2. Describe how to prevent similar bugs from occurring in the future

More Debugging Prompts

Debugging
Hot

Fix Null Pointer Exception

A specialized prompt to help debug **NPEs** and identify the **root cause** of null references.

I am getting a NullPointerException in Java at this line: [Insert Code]. Can you trace where the null value might be coming from and suggest a production-grade fix?

Debugging
Hot

Fixing React Re-Render Issue

Debug why a React component is re-rendering too often and optimize performance.

Act as a senior software engineer with 20+ years of real-world experience. Review the following React component that is re-rendering more than it should. Assume the code is flawed until proven otherwise.

Walk through the component line by line and explain exactly why it re-renders, what is triggering each render, and which parts of the code are poorly designed or outright wrong. Identify unnecessary state updates, unstable references, misuse of hooks, or any architectural mistakes that lead to wasted renders.

Provide clear, opinionated fixes using best practices such as React.memo, useMemo, useCallback, or better state and component boundaries. If something should be refactored, say so directly and explain why.

Don't just patch the issue. Improve the code's performance, readability, and long-term maintainability as if this were production code you'd have to own. Ensure the final solution is idiomatic, efficient, and compatible with modern React standards.

Code to review: [Insert Code]

Debugging
Hot

Works on My Machine, Fails in Production

Analyze why code behaves differently across environments and fix the real root cause.

Act as a senior software engineer with over 20 years of production experience.

CONTEXT: The following code works locally but fails in another environment (staging or production). Assume this is an engineering failure, not bad luck.

YOUR TASK:

  • Walk through the code execution step by step
  • Identify environment-specific behavior, hidden dependencies, and incorrect assumptions
  • Call out fragile logic, poor error handling, reliance on local state, filesystem quirks, timing assumptions, and dependency differences

ANALYSIS REQUIREMENTS:

  • Provide a clear root-cause analysis supported by evidence from the code or execution flow
  • Explain what logs, signals, or checks would confirm the diagnosis before applying a fix

SOLUTION EXPECTATIONS:

  • Propose a robust, production-grade solution, not a band-aid
  • Refactor or redesign any part that would not survive real-world production conditions
  • Improve observability, error reporting, and defensive checks

VALIDATION:

  • Explain how the fix can be validated
  • Describe how it prevents similar failures in the future

INPUT: Code: [Insert Code] Failure context: [Local works / Production fails details]