AI Prompts for Repeated Error Diagnosis and Fixing

Please quote the exact error message produced in the last run. Then, compare it to the expected output based on my previous instructions. Highlight any discrepancies between the two, and provide a brief analysis of why these discrepancies may have occurred and how to address them moving forward.

Please analyze the following build error message from the deployment tab: [BUILD ERROR MESSAGE]. Identify any patterns or repeated mistakes within this error that may indicate underlying issues. Provide a detailed explanation of each identified pattern, including potential causes and suggestions for how to address these mistakes effectively.

Please explain your interpretation of my original instruction before retrying the last command. Include specific details about what you understood and any potential misunderstandings that could have contributed to the repeated error. This will help ensure we are aligned and can move forward effectively.

Identify the expected behavior of the application in comparison to the actual behavior observed during the last run. Please provide a detailed list that includes the correct output that should have been generated and explain how it differs from the output that was actually produced. Additionally, highlight any specific conditions or inputs that may have influenced this discrepancy. Format your response in a clear table with columns for "Expected Behavior," "Actual Behavior," and "Differences.

Identify the specific rule or constraint that was violated in your last output. Please quote the exact clause from my instructions that you failed to adhere to and provide an explanation of how this violation impacted the overall output. Additionally, suggest a revised approach that aligns with the instructions to avoid similar mistakes in the future.

Please revert the function signature at 'src/app.js:45' back to its original form: 'function calculateTotal(price, tax)'. Before applying this change, provide a diff of the modifications made to the function signature. Ensure that the output clearly shows the differences between the current and original signatures, highlighting the specific changes.

Rewrite the database connection configuration in 'config.js' to ensure it matches the required format. The original line is 'db.connect(url)'. Change it to 'db.connect({ url: process.env.DB_URL })'. After making the change, please confirm that the new configuration is correctly implemented and provide a brief explanation of why this format is necessary for secure database connections.

Please modify the error handling in the file 'src/utils/errorHandler.js' to include a specific case for 'DatabaseConnectionError'. Add the following line of code: 'if (error instanceof DatabaseConnectionError) { handleDatabaseError(); }'. Make sure that this change is limited strictly to the error handling section and does not affect other parts of the code. After making the change, provide a brief explanation of how this improves error handling.

Please ensure that all files in the 'src' directory adhere to the ESLint rules defined in '.eslintrc.json'. First, run the linter to identify any violations. Then, provide a detailed report of the issues found, specifically highlighting problems related to indentation and semicolon usage. Finally, suggest the necessary changes to fix these violations and ensure consistent code formatting throughout the directory.

Please verify the dependency imports in the file 'src/index.js'. Specifically, check if 'express' and 'mongoose' are correctly imported. If you find any missing or incorrect imports, provide the corrected code snippet with the necessary changes highlighted, and explain why each correction is important for the functionality of the application.

Please run the test suite for the project and confirm that all tests pass without errors. Focus particularly on the tests related to the recent changes made in the codebase. Provide a summary of any tests that failed, including the reasons for failure and any relevant error messages.

Please display the diff of the file 'src/app.js' after applying the changes. Ensure that the output highlights the specific lines that were modified, added, or removed. Additionally, provide a brief explanation of how these changes address the original issues and confirm that no unintended modifications have been introduced.

Re-run the last command that resulted in the repeated error: [LAST COMMAND]. Confirm whether the same error message, [ERROR MESSAGE], appears again or if the issue has been resolved. Provide a summary of your findings, including any changes in behavior and potential next steps for troubleshooting if the error persists.

Please test the application by inputting the following edge cases that previously caused failures: [EDGE CASE 1], [EDGE CASE 2], and [EDGE CASE 3]. Verify that the application processes these inputs correctly and does not revert to the previous error. After testing, provide a detailed report on the results, including any errors encountered and how they were resolved.

Please check the output of the file 'src/output.js' after the recent fixes. Confirm whether it matches the expected results by providing the actual output alongside the expected output for comparison. Additionally, if there are discrepancies, briefly explain what the differences are and suggest possible reasons for these variations.

Please create a deployment validation pre-check checklist that includes the following steps: first, confirm that the database connection is established. Next, verify that all environment variables are correctly set. If any of these checks fail, ensure the process stops and logs an appropriate error message before proceeding. Format the output as a clear, step-by-step checklist for developers to follow prior to deployment.

Please add a comment at the top of the file 'src/utils/errorHandler.js' that states: 'Ensure all errors are handled gracefully. Follow the protocol for [ERROR TYPE] and other critical errors to prevent application crashes during runtime.' Additionally, provide a brief explanation of the importance of error handling in maintaining application stability and suggest best practices for handling different types of errors.

Please create a comprehensive code review checklist that I can use for every pull request. The checklist should include the following items: check for correct function signatures, validate database configurations, ensure all dependencies are imported correctly, and include additional best practices for code quality and maintainability. Format the checklist in a clear and organized manner, with each item listed separately for easy reference.

Before proceeding with any deployment, please conduct a self-check to ensure the following criteria are met: all tests must pass, there should be no critical errors present in the logs, and all configurations must be validated. If any of these checks fail, provide a detailed report of the issues encountered and halt the deployment process until all criteria are satisfied.

Please create a pre-deployment verification message for the deployment process. The message should read: "Confirm that all required environment variables are set. If any are missing, log an error and stop the deployment." Additionally, outline the steps the system should take to check for these variables, including how to log the error and halt the deployment process if any required variables are not present.