AI Prompts for Identifying Repeated Error Causes

Quote the last output you produced regarding the function at [FILE]:[LINE]. Then, compare this output to the expected result based on my previous instructions. Highlight the differences between the two outputs and specify what was required in the expected output that was not met. Provide a clear summary of the discrepancies and any potential reasons for the errors.

Please paste the exact error message from your last build attempt: [ERROR MESSAGE]. Analyze this message to identify discrepancies between the expected behavior and the actual behavior of the application. Provide a detailed breakdown of the error, including potential causes and suggested solutions to resolve the issue. Format your response in a structured manner, outlining each point clearly.

Please interpret my last instruction regarding [SPECIFIC FUNCTION]. Clearly explain your understanding of what was requested, including any key details or potential areas of confusion. After your interpretation, confirm if you are ready to proceed with executing the instruction again based on this clarification.

Create a structured comparison table that lists the expected behavior of [SPECIFIC COMPONENT] alongside the actual behavior observed. For each entry, clearly outline the discrepancies and provide a brief explanation of how these differences indicate where the process failed. Ensure the table includes columns for the expected behavior, actual behavior, and a description of the failure.

Identify the specific rule or constraint that was violated in your last output. Please quote the exact clause that outlines this constraint to clarify the expected behavior. Additionally, provide a brief explanation of how this violation occurred and suggest a corrective action to prevent it in future outputs. Format your response clearly, separating each part for easy reference.

Identify the incorrect function signature in the file located at [FILE] on line [LINE]. The original signature is as follows: [PASTE]. Please provide the diff of the changes needed to revert the signature back to the original format, and display this diff before any modifications are applied.

Rewrite the component located at [FILE] on line [LINE] to include a validation constraint that checks for [SPECIFIC CONDITION] before any further processing occurs. Make sure to implement this constraint clearly in the logic, and provide a brief explanation of how it improves the overall functionality. Additionally, include any necessary error handling to manage cases where the condition is not met.

Adjust the dependency at [FILE]:[LINE] to match the version specified in my previous instructions. Please confirm that this version is compatible with the rest of the project by checking for any conflicts or issues that may arise. Provide a brief summary of your findings and any necessary steps to resolve potential compatibility problems.

Please review the function located at [FILE]:[LINE] to ensure that its output format strictly adheres to the specified structure: [PASTE FORMAT]. Validate the output format before executing the function and provide feedback on any discrepancies found. If the format does not match, suggest specific changes needed to comply with the required structure.

Please verify the imports in [FILE]. Ensure that each import exists in the file tree and is correctly referenced. For any imports that are missing, mark them as UNVERIFIED and suggest appropriate alternatives. Present your findings in a structured report that includes the original import, its status, and the recommended alternatives for each missing import.

Please run a test on the function located at [FILE]:[LINE] to verify that it behaves as expected. After conducting the test, provide a detailed report that includes the results, any issues encountered, and whether the functionality meets the specified requirements. Additionally, include any recommendations for further improvements if necessary.

Please provide a detailed diff of the changes made to [FILE] at [LINE]. Include a side-by-side comparison of the original and modified lines, highlighting the specific adjustments that were applied. Additionally, summarize the implications of these changes and confirm whether they address the issues identified in the previous review.

Replay the original scenario that caused the error in [FILE]. Please provide a detailed account of the steps taken during the replay, noting any discrepancies or changes in behavior. Additionally, confirm whether the error persists or if it has been resolved, and summarize your findings in a brief report.

Please analyze the function located at [FILE]:[LINE] to verify its handling of edge cases. Specifically, test the function with the inputs that previously caused failures and document the outcomes. Provide a summary of whether the function now handles these edge cases correctly, along with any recommendations for further improvements if necessary.

Verify the output state of [SPECIFIC FUNCTION] after applying the fix. Please confirm that it matches the expected output format and values. If there are discrepancies, provide a detailed explanation of the differences and any potential implications for further testing or development.

Please provide a clear and concise session-opening constraint for the project related to error handling. Use the following format: 'Before any execution step: verify that the function signatures match the expected formats. If discrepancies occur, stop and report the issue before continuing. Never execute without confirming the signatures.' Ensure that the output is formatted for easy copying and pasting.

Please generate a project specification message that includes the following instructions: 'Before any build step, verify that all dependencies in [PACKAGE.JSON] are correctly installed and match the specified versions. If any are missing, report them before proceeding.' Ensure the message is clear and concise, suitable for inclusion in a project documentation or checklist format.

Draft a naming convention message for function signatures that states: "All functions must adhere to the following signature format: [SPECIFIC FORMAT]. Any deviation from this format must be flagged before execution to ensure consistency and prevent errors." Please provide the exact text for this message, including any necessary examples or clarifications.

Please create a self-check request that instructs the AI to verify the output format of all functions before execution. The request should state: 'Verify the output format of all functions before execution. Ensure they match the required structure: [SPECIFIC FORMAT]. If not, stop and report the issue.' Present this request in a clear and structured format.

Create a conversation-starter template for a pre-execution validation checklist that includes the following points: 1. Ensure all function signatures are correct. 2. Verify that all dependencies are installed. 3. Validate the output formats. If any of these checks fail, specify how to report the issues. Format the output as a clear checklist that can be easily referenced before executing any code.