AI Prompts for Correct File Editing Behavior

Please quote the exact file path that was modified in your last edit. Then, compare this file path to the specified file path: [SPECIFIC FILE PATH]. Highlight any discrepancies you find between the two paths and provide a brief explanation of their significance.

Please analyze the output log from the last edit attempt that shows which file was modified. Compare this information to the intended file specified as [SPECIFIC FILE PATH]. Provide a summary of whether the modified file matches the intended file, and if there is a discrepancy, explain the potential reasons for the mismatch.

Please explain your understanding of my request to edit [SPECIFIC FILE PATH] before making any changes. Include details about the specific edits you believe are necessary, the purpose of these changes, and any potential implications they may have on the overall project. This will help ensure that we are aligned and prevent any misinterpretations.

Please provide a detailed comparison of the expected changes to [SPECIFIC FILE PATH] against the actual changes that were made. For each change, clearly list what was expected and what was actually applied, and indicate whether each change was implemented correctly or not. Format the output in a table with columns for "Expected Change," "Actual Change," and "Status.

Identify the specific rule or constraint that was violated in the last edit of the document. Please provide the exact clause from the previous instructions that was not followed, and explain how this violation impacts the overall document integrity. Format your response to include the rule, the context of the edit, and any recommendations for correcting the issue.

Please correct the file editing command for the file located at [SPECIFIC FILE PATH]. The original command is: [PASTE]. The corrected command should be: [PASTE]. Ensure that only the corrected command is applied and provide a brief explanation of why the correction is necessary.

Rewrite the editing command to explicitly target the file located at [SPECIFIC FILE PATH]. Make sure that the command does not reference any other files or directories. Provide the revised command in a clear format, ensuring it is ready for immediate use without any ambiguity.

Please make a scoped change to [SPECIFIC FILE PATH] only. Ensure that this operation does not modify any other files in the project. After completing the change, provide a summary of what was altered and confirm that no unintended modifications occurred in other files.

Please verify the format of the file located at [SPECIFIC FILE PATH] before proceeding with any edits. Ensure that it complies with the required structure and does not conflict with the formats of other related files. If any inconsistencies are found, provide a detailed report on the issues and suggest necessary corrections to achieve format consistency.

Please verify the import statements in the file located at [SPECIFIC FILE PATH]. Identify any missing or incorrect dependencies and provide a detailed list of the issues found. For each issue, suggest the necessary corrections and explain why these changes are important for the functionality of the code.

Please run a test on the edited file located at [SPECIFIC FILE PATH] to verify that all changes have been applied correctly. After running the test, provide a detailed report of any discrepancies found in the output, including specific examples of what differs from the expected results. Additionally, summarize the overall success of the changes made.

Display the diff of changes made to [SPECIFIC FILE PATH] compared to its previous version. Ensure that only the intended changes are present and provide a summary of any unintended modifications. Additionally, highlight the specific lines that were altered, added, or removed, and explain the significance of these changes in the context of the overall project.

Replay the original scenario where the edit was made to [SPECIFIC FILE PATH]. Please provide a detailed account of the actions taken during the edit, including any relevant timestamps or changes made. After reviewing the scenario, confirm whether the correct file was modified and outline any discrepancies or issues that may have arisen during the process.

Please examine the file located at [SPECIFIC FILE PATH] to identify any edge case regressions that may have occurred due to the last edit. Provide a detailed report on any affected functionalities, including a description of the issues found and suggestions for resolution. Ensure that you confirm whether all intended functionalities remain intact after the changes.

Please verify the final output state of [SPECIFIC FILE PATH] after the last edit. Check that it accurately reflects the intended changes and that there are no unintended modifications. Provide a summary of your findings, highlighting any discrepancies or confirming that the file is as expected.

Please implement a session-opening constraint that requires confirmation of the target file path before any file edit. The confirmation should check if the path matches [SPECIFIC FILE PATH]. If the path does not match, the operation should be halted, and the user should be notified with an appropriate message explaining the reason for the halt.

Please create a conversation-starter template for confirming file edits. The template should include a prompt that asks the user to verify the file path before proceeding with any edits. Specifically, it should state: 'Before proceeding with edits, confirm the file to be edited is [SPECIFIC FILE PATH]. If it is not, please stop and clarify the intended target.' Ensure the template is clear and encourages users to double-check their selections.

Draft a project specification message that emphasizes the importance of confirming all edits against the target file located at [SPECIFIC FILE PATH]. Include a clear statement that any deviation from this protocol will necessitate a re-evaluation of the edit request. Ensure the message is concise yet informative, outlining the rationale behind this requirement and the potential consequences of non-compliance.

Create a message to remind users about the importance of consistent file naming conventions. The message should state: 'Please ensure that all files are named consistently with [SPECIFIC FILE PATH] to avoid confusion during edits.' Additionally, provide examples of correct and incorrect file names to illustrate the convention clearly.

Please create a self-check request for editing commands. The request should state: 'Before executing any edit command, verify that the target file is [SPECIFIC FILE PATH]. If the file does not match, notify the user to confirm the correct file before proceeding with the edits.' Ensure the notification is clear and prompts the user for confirmation.