AI Prompts for Handling Async Errors Properly

Please identify all asynchronous functions in the project and highlight those that lack proper error handling. For each function, provide a brief description of its purpose and specific examples of potential errors that could arise during execution. Additionally, suggest best practices for implementing error handling in these functions to improve overall reliability and robustness of the code. Format your response as a detailed report with clear sections for each function identified.

Review the following async function: [PASTE FUNCTION]. Analyze the code to determine if it includes appropriate error handling mechanisms, such as try-catch blocks, and whether it properly propagates errors to calling functions. If you identify any issues, explain the potential consequences of these shortcomings and suggest improvements to enhance error handling in the function. Provide your analysis in a structured format, including code snippets where applicable, and summarize your findings in a clear conclusion.

Analyze the error propagation mechanism in the function [FUNCTION NAME]. Explain the current approach to handling errors, detailing how they are communicated through the system. Identify any potential weaknesses or areas for improvement in this process, and provide specific recommendations on how to enhance error handling and ensure more robust performance. Include examples of best practices for error propagation that could be applied to improve the function's reliability.

Please review the error logging mechanism implemented in the asynchronous functions of the project. Assess whether errors are being logged consistently across different scenarios and identify any gaps or inconsistencies in the logging strategy. Provide detailed feedback on the effectiveness of the current approach, including suggestions for improvement and best practices for error handling in asynchronous contexts. Additionally, outline any potential impacts on debugging and maintenance if the logging is not adequately addressed.

Please evaluate the clarity and usefulness of the error messages generated by the following function: [PASTE FUNCTION]. Identify any areas where the messages may be ambiguous or unhelpful for debugging purposes. Provide specific suggestions for enhancing these messages to improve their clarity and effectiveness, ensuring that they guide the user in diagnosing issues more efficiently. Additionally, explain how the proposed changes could lead to a better debugging experience.

Please add try-catch blocks to the following asynchronous function: [PASTE FUNCTION]. Ensure that all potential errors are caught and handled appropriately within the blocks. Additionally, provide meaningful error messages that can help in debugging if an error occurs. The final code should maintain the original functionality of the function while ensuring robust error handling.

Please modify the function [FUNCTION NAME] to ensure that errors are propagated correctly to the caller. Describe the specific changes you made to the function, including any adjustments to the error handling logic and how these changes improve the overall error management. Additionally, provide examples of how the function behaves before and after the modifications, and explain the potential impact on the calling code when an error occurs.

Please enhance the error logging in the function [FUNCTION NAME]. Ensure that all errors are logged with comprehensive context, including the error message, stack trace, and any relevant variable values at the time of the error. Provide the updated code in a clear format, and include comments explaining the changes made to improve the logging process. Additionally, suggest any best practices for error handling that could further enhance the robustness of the function.

Refactor the error messages in the function [FUNCTION NAME] to enhance clarity and provide actionable guidance. For each error message, provide a before and after example that illustrates the changes made. Ensure the new messages clearly convey the issue and suggest steps the user can take to resolve it. Aim for a tone that is helpful and informative, and include any relevant context that may assist users in understanding the errors.

Create comprehensive test cases for the function [FUNCTION NAME] to ensure that all potential errors are caught and handled appropriately. Include scenarios for both synchronous and asynchronous errors, detailing the expected outcomes for each case. After running the tests, provide a summary of the results, highlighting any errors that were not handled as expected and suggesting possible improvements to the error handling logic. Format the results in a clear and organized manner for easy review.

Please run all test cases related to asynchronous error handling in the application. Verify that each test case executes successfully and confirm that there are no unhandled errors present in the system. Provide a detailed report outlining any errors that were encountered, along with their specific locations in the code. Additionally, include recommendations for improving error handling based on the test results.

Please review the error logs generated after running the application. Ensure that all logged errors adhere to the new format specified in the documentation. Provide a summary of any discrepancies found, including the number of errors that do not match the format and specific examples of those errors. Additionally, suggest any necessary steps to correct these issues and ensure compliance with the new logging standards.

Simulate various error scenarios in the application, including network failures, invalid inputs, and unexpected exceptions. For each simulated error, check if the new error messages are displayed as expected. Evaluate the clarity and helpfulness of these messages, ensuring they provide users with actionable information on how to resolve the issues. Document your findings in a structured format, highlighting any errors that do not meet clarity standards and suggesting improvements where necessary.

Please trace the error handling process in the application to confirm that errors propagate correctly to the top-level error handler. Start by identifying the different layers of the application where errors can occur, and describe how each layer handles errors before passing them up the chain. Include specific examples of error types that should be caught and how they should be reported to the top-level handler. Finally, provide recommendations for ensuring robust error propagation and handling throughout the application.

Please review the recent code changes made for error handling in the project. Summarize the key modifications, focusing on how they improve the handling of asynchronous errors. Confirm whether these changes have been correctly implemented and provide any recommendations for further improvements if necessary. Additionally, include any potential edge cases that should be tested to ensure robust error handling.

Draft a comprehensive section for CLAUDE.md that outlines best practices for handling asynchronous errors in software development. Include specific examples of effective error handling techniques, as well as common pitfalls that developers should avoid. Discuss the importance of proper logging, user feedback, and fallback mechanisms in maintaining application stability. Ensure the section is structured with clear headings and bullet points for easy readability, and aim for a length of at least 500 words to cover the topic thoroughly.

Please add detailed comments to the codebase that explain the error handling strategy implemented in the asynchronous functions. For each async function, include a brief description of its purpose, how errors are caught and managed, and any specific patterns or practices that are followed. Additionally, provide examples of potential error scenarios and how they are handled within the code. Ensure that the comments are clear and informative, making it easy for future developers to understand the rationale behind the error handling approach.

Propose a naming convention for asynchronous functions that clearly indicates the implementation of error handling. The convention should include specific prefixes or suffixes that convey the error handling aspect, such as using "handle" or "withError" in the function name. Provide at least five examples of function names that follow this convention, along with a brief explanation of why each name effectively communicates the presence of error handling. Additionally, outline any guidelines for consistency in naming across different modules or components.

Please create a detailed checklist for developers to follow when starting a coding session, focusing specifically on ensuring that asynchronous error handling is properly addressed. The checklist should include key steps such as reviewing existing error handling patterns, setting up appropriate logging mechanisms, and verifying that all async functions have proper try-catch blocks. Additionally, include reminders to test error scenarios and document any potential pitfalls. Format the checklist in a clear, numbered list for easy reference during coding sessions.

Create a project guard that automatically scans for missing error handling in asynchronous functions during code reviews. The guard should analyze the codebase and identify any async functions that lack proper error handling mechanisms. Provide a report detailing the specific functions that need attention, along with recommendations for implementing appropriate error handling strategies. Ensure that the output is structured and easy to understand, highlighting both the issues and suggested fixes.