AI Prompts for Correcting File Edit Errors

Please provide a list of all currently open files along with their respective paths. Additionally, identify which of these files corresponds to [FILE NAME] that I am referring to. Include any relevant details about the files, such as their last modified date or type, to help clarify the context. This information will assist me in understanding the current working environment better.

Please display the current project tree structure and highlight the file named [FILE NAME] within this structure. Additionally, provide a brief overview of the contents of this file, including its purpose and any relevant dependencies or relationships with other files in the project. Explain how this file fits into the overall architecture of the project and any potential issues that may arise from its current state. Format your response in a clear and organized manner.

Please verify the full path of the file associated with [FILE NAME]. I need you to check if the path matches the specified request and provide a confirmation. If there are any discrepancies, please detail what the correct path should be and explain why it differs from my request. Additionally, if the file is not found, provide suggestions on how to locate it.

Assess the context retention of your current session. Please provide a detailed list of all the files you have interacted with during this session, including their names and types. Additionally, confirm whether you still retain context for [FILE NAME], explaining what specific details or information you remember about it. If there are any files for which you have lost context, please specify which ones and describe what information is missing.

Please read the .cursorrules file and analyze which rules apply to the specified file [FILE NAME]. Provide a detailed summary of each applicable rule, including whether they are currently active or inactive. Additionally, explain the implications of these rules on the file's processing and any potential issues that may arise if the rules are not applied correctly. Format your response in a clear and organized manner, highlighting key points for easy reference.

Please focus exclusively on the file located at [FILE PATH]. Confirm that this file is now the active context for all subsequent actions. Additionally, provide a brief summary of the contents of this file and any relevant details that may assist in understanding its purpose. Ensure that any changes or edits made will pertain solely to this file.

Please revert the changes made to the previously edited file and apply the same changes to the file located at [CORRECT FILE PATH]. Ensure that all modifications are accurately transferred and that the integrity of the new file is maintained. Provide a summary of the changes that were reverted and the adjustments made to the correct file. Confirm that the correct file is now updated and ready for further use.

Please confirm the full path of the file named [FILE NAME] before I proceed with any changes. I need to ensure that this path matches the intended target location. If there are any discrepancies, provide guidance on how to correct them. Additionally, outline the steps I should take to verify the file's integrity and ensure that I am editing the correct version.

Please reapply the context rules from the specified .cursorrules file to the document located at [FILE PATH]. Ensure that all relevant rules are correctly implemented and functioning as intended. After applying the rules, provide a confirmation that they are now active, along with a brief summary of any changes made or issues encountered during the process.

Please isolate the file named [FILE NAME] for editing. Focus solely on this file and do not reference or consider any other files during this process. Provide a summary of the current content and any necessary changes that need to be made. Once the edits are completed, outline the steps taken and confirm that no other files were affected.

Please provide a comprehensive list of all files that were edited during the last operation. Additionally, confirm whether [FILE NAME] is the only file that underwent changes. Include details such as the date and time of each edit, the nature of the changes made, and any relevant context that may help in understanding the modifications. Format the response in a clear and organized manner for easy reference.

Please display the before and after states of the file named [FILE NAME]. Include a side-by-side comparison that highlights the specific changes made, such as additions, deletions, and modifications. Additionally, provide a brief summary of the key differences between the two versions and confirm whether the changes align with the intended updates. Ensure that the format is clear and easy to understand for review purposes.

Please run a series of tests specifically related to [FILE NAME]. Ensure that the tests cover all critical functionalities and edge cases that may be affected by the recent changes. After executing the tests, provide a detailed output report that includes any errors encountered, the results of each test case, and a summary of whether the changes are functioning as expected. Additionally, highlight any areas that may require further attention or testing.

Please reproduce the original scenario that necessitated the edit to [FILE NAME]. Describe the steps taken to encounter the issue and provide details on the specific conditions under which it occurred. After reproducing the scenario, confirm whether the issue still persists or if it has been resolved. Include any relevant observations or changes in behavior that may indicate a successful resolution.

Please verify that the changes made to [FILE NAME] are in compliance with the rules outlined in the .cursorrules document. Provide a detailed comparison of the changes against the specified rules, highlighting any discrepancies or violations found. Include a summary of the key areas where compliance is met and where it falls short, along with suggestions for adjustments to ensure full adherence to the rules. Format the response clearly, using bullet points for discrepancies and a brief conclusion on the overall compliance status.

Please create a new rule for the .cursorrules file that ensures edits are only applied to [FILE NAME] when specific conditions are met. The rule should include criteria for identifying when the edits should be allowed, such as checking for certain keywords or file properties. Additionally, outline any exceptions to this rule and provide a brief explanation of how this will prevent future occurrences of editing the wrong files. Format the rule clearly for easy implementation.

Create a comprehensive checklist to ensure all necessary steps are followed before starting any editing session for [FILE NAME]. The checklist should include: verifying the correct file is targeted, reviewing the previous version for context, confirming access permissions, and ensuring all relevant stakeholders are informed of the session. Additionally, include a step to prepare a backup of the current file before making any changes. Format the checklist in a clear, numbered list for easy reference during the session.

Please add a comment above the main function in [FILE NAME] that warns AI assistants about the specific file targeting requirement. The comment should clearly state the importance of ensuring that the correct file is being edited to prevent any unintended changes. Include a brief explanation of the potential consequences of editing the wrong file and emphasize the need for caution. The comment should be concise yet informative, ideally no more than three sentences long.

Draft a comprehensive project convention for naming and organizing files that will help minimize targeting errors in future sessions. Include guidelines on file naming structures, such as using specific prefixes or suffixes to indicate file versions or types. Outline best practices for folder organization, including how to categorize files by project phase, team member responsibilities, or file types. Additionally, suggest a review process to ensure adherence to these conventions and provide examples of correctly named and organized files for reference.

Please draft an opening message for editing sessions that clearly confirms the specific file being targeted for edits. The message should include a request for the file name and any relevant details about the edits needed. Aim for a friendly yet professional tone, ensuring that the recipient feels comfortable providing the necessary information. The message should be concise, ideally no longer than three sentences, and should encourage clarity to prevent any misunderstandings during the editing process.