AI Prompts for Identifying Incorrect File Edits

Please quote the exact output from your last edit attempt, including the file path and the specific changes made. Then, compare this output with the intended file path, which is [SPECIFIC FILE PATH]. Provide a summary of any discrepancies between the two, highlighting what was edited incorrectly and suggesting how to correct it.

Please analyze the output log from the last edit attempt for the file [FILE NAME]. Focus specifically on the section that details the changes made, and identify any discrepancies or errors that may explain why the wrong file was modified. Provide a summary of your findings, including potential causes and recommendations for avoiding similar issues in the future.

Please provide your interpretation of my instruction to edit [SPECIFIC FILE]. Include any assumptions you are making about the changes required and the context of the edits. This will help us identify any potential miscommunication before proceeding with the actual editing process.

Please provide a structured comparison of the expected changes for [SPECIFIC FILE] versus the actual changes made. Present this information in a table format with two columns: one for the expected changes and another for the actual changes. Include specific details for each change to highlight discrepancies and ensure clarity in the comparison.

Please analyze the recent file edits and identify the specific rule or constraint that was violated during the editing process. Quote the exact clause from the guidelines that led to the incorrect file modification. Provide a summary of how this violation occurred and suggest steps to prevent similar mistakes in the future.

Please revert the changes made to [SPECIFIC FILE] back to its original state without altering any other files. Before applying the changes, provide a detailed diff of the modifications that will be reverted. Ensure that the output clearly highlights the differences between the current version and the original version of the file.

Rewrite the function in [SPECIFIC FILE] to match the original signature of [PASTE ORIGINAL SIGNATURE]. Make sure to only modify the function as specified and avoid any other changes to the code. After completing the rewrite, provide a brief summary of the changes made and confirm that the function behaves as expected.

Please make a scoped change to [SPECIFIC FILE] by modifying only the lines specified in [LINE NUMBERS]. Ensure that no other parts of the file are altered. After making the changes, provide a brief summary of what was changed and why it was necessary.

Please review the formatting in [SPECIFIC FILE] to ensure it adheres to the project's style guide. Identify and highlight any deviations from the required format, and provide specific corrections for each issue found. Additionally, summarize the changes made to ensure consistency throughout the file.

Verify the import statements in [SPECIFIC FILE] and ensure that all dependencies are accurately referenced. List any missing dependencies and provide the necessary code to add them. Additionally, explain the purpose of each dependency in the context of the file's functionality.

Run the application and conduct a thorough test on the functionality of [SPECIFIC FILE]. Ensure that it behaves as expected by checking all relevant features and interactions. If you encounter any errors or unexpected behavior, document them clearly, including steps to reproduce the issue and any relevant error messages.

Display the diff of the recent changes made to [SPECIFIC FILE]. Confirm that only the intended modifications were applied by highlighting the differences between the current version and the previous version. Provide a summary of the changes and indicate any unintended modifications that may have occurred.

Please replay the original scenario where the wrong file was edited in Replit. Detail the steps taken during that scenario, and confirm whether the issue still occurs or if it has been resolved. Provide a summary of any changes made and the outcome of your testing.

Examine the edge cases related to [SPECIFIC FILE] to verify that the recent changes have not introduced any regressions. Please provide a detailed report that includes a list of identified edge cases, the expected outcomes, the actual outcomes after the changes, and any discrepancies found. Additionally, suggest potential fixes or further testing needed for any issues identified.

Confirm the state of [SPECIFIC FILE] after the recent edits have been made. Please provide a detailed summary of its current content, highlighting any changes that were implemented and ensuring that it aligns with the expected outcome. Additionally, note any discrepancies or issues that may still need to be addressed.

Please create a detailed file targeting constraint for the project. The constraint should state: 'Before any edit is made, the system must confirm that the target file is [SPECIFIC FILE]. If the target file does not match, the operation should be halted, and the user must be notified with a clear message explaining the mismatch.' Ensure the output is structured as a formal specification document.

Please create a conversation-starter template for confirming file edits. The template should include a prompt that states: 'Before proceeding with any edits, confirm the target file is [SPECIFIC FILE]. If it is not, please stop and clarify the intended target.' Ensure the wording is clear and encourages users to double-check their selections before making any changes.

Please add a comment guard in [SPECIFIC FILE] that states: 'WARNING: Any changes here must be confirmed with the user to avoid incorrect modifications.' Ensure that this comment is placed at the top of the file for visibility. Additionally, provide a brief explanation of why this guard is important for preventing incorrect modifications and how it should be implemented in the code.

Create a project convention message that emphasizes the importance of verifying the file path before making any edits. Include a reminder to use [SPECIFIC FILE] as the primary target for all related changes. The message should be clear and concise, outlining the potential consequences of not following this convention and encouraging team members to double-check their work.

Please create a self-check request for file editing processes. The request should state: 'Before executing any file edit, confirm that the intended file is [SPECIFIC FILE]. If it is not, halt the operation and provide clarification on the instruction needed to proceed correctly.' Ensure this request is clear and easy to follow for users.