20 of the best prompts for handling null values in code, step by step across 4 stages. Works with ChatGPT, Claude, and Gemini.
20 of the best prompts for handling null values in code, step by step across 4 stages. Works with ChatGPT, Claude, and Gemini.
Published June 28, 2026
Null or undefined values in generated code can cause runtime crashes, disrupting the application's functionality. These crashes lead to unexpected behavior and can be difficult to debug. These prompts help developers identify and fix null handling issues, ensuring stable and reliable code execution. Built across 4 distinct stages covering Diagnose the Wall, Isolate and Fix, Verify the Resolution and more, this guide gives you one expert prompt per step so you never have to write from scratch or guess what the AI needs. The prompts work in ChatGPT, Claude, and Gemini and are designed to get usable output on the first try.
Identify where null or undefined values are causing issues in the code.
Identify Null Occurrences
Please scan the codebase for any instances where null or undefined values are used without proper checks. Create a detailed report that includes the specific locations in the code where these occurrences are found. For each instance, suggest improvements or best practices to handle these null values effectively. Additionally, provide examples of how to implement these improvements in the code to enhance its robustness and prevent potential runtime errors.
Analyze Recent Errors
Please analyze the recent error logs from the application and identify any instances of null or undefined value errors. Provide a detailed summary of your findings, including the frequency of these errors and any patterns you observe. Additionally, suggest potential causes for these errors, considering factors such as recent code changes, data input issues, or environmental factors. Format your response in a clear report style, highlighting key insights and recommendations for addressing these issues.
Check Function Parameters
Inspect the following function definitions for parameters that may receive null or undefined values: [FUNCTION_DEFINITIONS]. For each function, identify which parameters are at risk and provide a detailed explanation of why these checks are necessary. Additionally, suggest appropriate null or undefined checks that should be implemented for each identified parameter. Format your response in a clear list, including the function name, the problematic parameters, and the recommended checks to ensure robust error handling.
Review Variable Initializations
Please review the variable initializations throughout the codebase to identify any instances where variables may be unintentionally set to null or undefined. Provide a detailed list of these problematic initializations, including the specific locations in the code where they occur. Additionally, explain the potential impact of each issue on the overall functionality of the application. If possible, suggest best practices for initializing variables to avoid these issues in the future.
Evaluate Conditional Statements
Identify and evaluate the conditional statements in the code that may not properly handle null or undefined values. For each statement, provide a specific example of where the issue occurs and explain why it could lead to errors or unexpected behavior. Additionally, recommend modifications to ensure that these statements correctly account for null or undefined values, including best practices for implementing these checks. Summarize your findings in a clear and structured format.
Focus on implementing fixes for identified null handling issues.
Add Null Checks
Please review the following code snippet for potential null or undefined value issues. Identify all locations where null checks need to be added and insert them accordingly. Show the updated code with clear comments explaining each change made, including the rationale behind adding each null check. Ensure that the final code is clean, well-structured, and maintains the original functionality while preventing errors related to null values.
Refactor Functions
Refactor the following functions to handle null or undefined parameters gracefully: [FUNCTION NAMES]. For each function, provide the updated code that includes appropriate null checks and default values where necessary. Additionally, explain the improvements made in terms of code robustness, potential error reduction, and overall readability. Ensure that the refactored code is well-commented to clarify the changes and the reasoning behind them.
Update Initializations
Please review the following code snippet and modify the variable initializations to ensure that none are set to null or undefined. Present the revised code with clear explanations for each change made, detailing why the new initializations are preferable. Additionally, include any potential implications of these changes on the overall functionality of the code. The response should be structured in a way that highlights the original code, the revised code, and the justifications in a clear and organized format.
Enhance Conditionals
Please enhance the conditional statements in the following code snippet to properly handle null or undefined values. Ensure that each conditional is robust against these cases and does not lead to runtime errors. After making the improvements, display the enhanced code along with clear annotations explaining the changes made and the reasoning behind them. The code snippet to improve is: [INSERT CODE SNIPPET HERE].
Implement Fallbacks
Please implement fallback mechanisms in the code for operations that may encounter null or undefined values. Ensure that each operation is wrapped with a check that provides a default value or alternative behavior when a null or undefined value is detected. Include comments in the code to explain the purpose of each fallback and how it enhances the robustness of the application. Show the complete code with the new fallbacks integrated, and provide a brief summary of how these changes improve error handling.
Ensure that the null handling issues have been resolved and the code is stable.
Run Null Tests
Please execute a series of tests to check for the handling of null or undefined values in the codebase. Ensure that each test covers different scenarios where null values may occur, and document the results in a structured format. Include details such as the test case description, whether it passed or failed, and any errors encountered during the tests. After completing the tests, provide a summary report confirming the absence of related errors and any recommendations for improving null handling if issues are found.
Review Error Logs
Please analyze the latest error logs for the project related to [PROJECT NAME] to verify whether null or undefined value errors have been resolved. Provide a summary of your findings, including the number of errors identified, the specific types of errors that were present, and whether they have been successfully addressed. Additionally, highlight any remaining issues that may need further attention and suggest potential solutions or next steps to ensure all errors are fully resolved. Format your response as a detailed report.
Check Code Coverage
Please evaluate the code coverage for the project related to [PROJECT NAME] to ensure that all null handling paths are adequately tested. Generate a detailed coverage report that includes the percentage of code covered, identifies any untested paths, and highlights specific areas where null checks are missing. Additionally, provide recommendations on how to improve the coverage and ensure robust null handling in the codebase. The report should be structured with clear sections for findings, gaps, and suggested actions.
Conduct Code Review
Please conduct a thorough code review of the provided code snippet, specifically focusing on improvements related to null handling. Identify any areas where null checks are missing and suggest best practices for implementing these checks effectively. Additionally, evaluate whether the current code adheres to established coding standards and conventions. Provide detailed feedback on your findings, including examples of how to enhance the code for better null safety and overall reliability. Format your response as a structured report with sections for findings, recommendations, and examples.
Validate User Scenarios
Please simulate a series of user scenarios that previously resulted in null or undefined errors in the [APPLICATION NAME]. For each scenario, outline the steps taken by the user and the expected outcomes. Confirm whether the issues have been resolved and provide detailed documentation of the results, including any error messages encountered, the conditions under which they occurred, and any changes made to prevent these errors in the future. Ensure that the documentation is clear and structured for easy reference.
Create mechanisms to avoid future null handling issues.
Draft CLAUDE.md Rule
Draft a new rule for CLAUDE.md that enforces the implementation of null checks in future code. The rule should clearly outline the importance of null checks, provide examples of correct and incorrect implementations, and specify the consequences of not adhering to this rule. Ensure the language is precise and suitable for inclusion in a coding standards document. Format the rule in a way that it can be easily understood and referenced by developers.
Add Code Comments
Please add detailed comments in the codebase that explain the importance of null checks. For each section of code where a null check is implemented, provide a brief explanation of why it is necessary and how it prevents potential errors or crashes. Include examples of both good and bad practices related to null checks, highlighting the consequences of neglecting them. Ensure that the comments are clear and informative, making it easy for future developers to understand the rationale behind the null checks.
Create Checklist
Create a comprehensive checklist for code reviews that focuses specifically on ensuring proper null handling in the codebase. Include items such as verifying that all variables are initialized before use, checking for null values in function parameters, ensuring that return values are validated for null, and confirming that appropriate error handling is in place for null cases. Additionally, outline best practices for documenting null handling decisions in code comments. Format the checklist in a clear, organized manner with bullet points for easy reference during reviews.
Define Naming Conventions
Help me establish clear naming conventions for indicating nullable variables in code. I want to ensure that these conventions are consistent and easily understood by all team members. Please provide specific examples of naming patterns that can be used, such as prefixes or suffixes, and guidelines on when to apply them. Additionally, include any best practices for documenting these conventions within our codebase to promote clarity and maintainability.
Set Up Project Guards
Create a detailed explanation of project guards designed to automatically flag potential null handling issues in a software project. Include an overview of how these guards function, the types of null handling issues they can identify, and the benefits of implementing them in the development process. Additionally, provide examples of scenarios where these guards would be particularly useful, and suggest best practices for integrating them into existing projects. Aim for a comprehensive guide that can help developers understand the importance of null checks and how to effectively use these guards.
Use Windsurf's custom rules feature to enforce null checks in your codebase. This ensures that all developers follow consistent practices, reducing the likelihood of null value errors.
Windsurf may not always account for null values in its autocomplete suggestions. Reviewing and updating the generated code to include null checks is essential to prevent runtime errors.
In Cascade mode, Windsurf can make autonomous edits, but it's crucial to review these changes to ensure they correctly handle null values without introducing new issues.
Incorporate null checks in all critical code paths and use Windsurf's custom rules to enforce these practices across your project. Regular code reviews can also help maintain quality.
Define specific rules in CLAUDE.md that mandate null checks and provide examples of correct implementations. This helps maintain consistent coding standards across the team.
AI Prompts for Adding Null Checks to Prevent Crashes
The generated code is failing to handle null or undefined values, leading to runtime crashes.
See promptsAI Prompts for Adding Null Checks to Generated Code
Generated code that does not handle null or undefined values can lead to runtime crashes, disrupting development.
See promptsAI Prompts for Handling Null Values in Code
Cursor-generated code is failing due to unhandled null or undefined values, causing runtime crashes.
See prompts