AI Prompts for Preventing Unwanted Code Changes

Please provide a detailed list of all files and functions that have been edited during this session. For each item, indicate whether it was explicitly mentioned in the last task description or if it was modified without prior request. Additionally, include a brief explanation of the changes made to each file or function, focusing on the purpose and impact of the unrequested modifications. Format the response in a clear and organized manner, making it easy to identify the differences between requested and unrequested changes.

Please review the changes made in the last task and identify any files or functions that were altered without being specified in the task description. Provide a detailed list of these scope violations, including the names of the files or functions, a brief description of the changes made, and an explanation of how these changes deviate from the original task requirements. Additionally, suggest potential impacts of these unasked changes on the overall project timeline and deliverables.

Please review the following task description: [PASTE TASK]. Identify and confirm the specific parts of the codebase that were intended to be modified based on this description. Additionally, provide a brief explanation of why each identified part is relevant to the task and any potential implications of not adhering to the task requirements. Format your response as a structured list, including the section of the codebase, its purpose, and the expected changes.

Please provide a detailed comparison of the files and functions that have been modified in relation to the original task description. Start by listing all modified files and functions, then analyze each one to determine if it aligns with the specified tasks. Identify any discrepancies, including any changes that were made that were not part of the original task. Additionally, explain the potential impact of these discrepancies on the overall project and suggest steps to address any issues found.

Please summarize any edits made that were not part of the specified task. Include details such as the file names, the specific functions that were altered, and a brief description of each unasked change. Additionally, highlight any potential impacts these changes may have on the overall project or functionality. Format the summary in a clear, organized manner, with bullet points for easy readability.

Identify and revert any changes made to files or functions that were not explicitly specified in the task description. Please provide a detailed list of the changes that were reverted, including the original state of each item and the reason for the reversion. Once the process is complete, confirm that all unwanted changes have been addressed and provide a summary of the actions taken.

Please restrict your edits to only the files and functions explicitly mentioned in the following task: [PASTE TASK]. Ensure that no changes are made to any other parts of the project that are not specified. Additionally, provide a brief summary of the rationale behind this restriction and any potential impacts on the overall project. This will help maintain focus and prevent scope creep during the development process.

Please undo the changes made to the following files/functions: [LIST FILES/FUNCTIONS]. Ensure that the restoration of these files/functions does not affect any other parts of the project. Provide a summary of the changes that were undone and confirm that the overall functionality remains intact. Additionally, include any potential impacts on related components that may need to be addressed.

Please re-evaluate the task description provided and confirm the exact scope of files and functions that need to be edited. Clearly outline which specific files will be affected and what functions require changes. Additionally, provide a brief rationale for why these particular files and functions were chosen, ensuring that the focus remains strictly within this defined scope. Format your response as a concise summary that highlights the key elements of the task.

Please lock the editing capabilities for any files that are not explicitly mentioned in the task description. Ensure that this restriction is applied to prevent any unintended changes to unspecified files. Once the locking process is complete, provide a confirmation that the settings have been successfully implemented.

Please verify that no files or functions outside the specified task scope of [TASK NAME] have been edited. Review the changes made and provide a detailed confirmation report. Include the names of any files or functions that were reviewed, and explicitly state whether any unauthorized edits were found. If everything is in order, summarize the findings in a clear and concise manner.

Please review the current edits made in this session and provide a detailed list. For each edit, indicate how it aligns with the original task description provided. Additionally, highlight any discrepancies or areas where the edits may deviate from the intended objectives. Include suggestions for adjustments if necessary to ensure all edits meet the task requirements.

Please conduct a compliance check on the project to verify that all edits align with the original task description. Ensure that no additional files or components have been altered beyond what was specified. Provide a detailed report outlining any discrepancies found, including specific sections or files that do not comply with the scope. Additionally, suggest corrective actions to address any identified issues and ensure adherence to the original project requirements.

Please validate the completion of the task titled [TASK NAME]. Ensure that only the specified changes, which are [LIST OF SPECIFIED CHANGES], have been implemented. If there are any discrepancies or unasked changes that have been made, highlight them clearly and provide a brief explanation of how they differ from the original instructions. Additionally, summarize the overall outcome of the task to confirm its alignment with the initial requirements.

Please conduct a thorough audit of the recent changes made to the project. Ensure that each change aligns with the original task description and does not introduce any unasked modifications. For each change, provide a detailed report highlighting any discrepancies, including specific examples of where the changes deviate from the task requirements. Additionally, suggest possible corrections or adjustments to bring the changes back in line with the original objectives.

Please draft a new rule for the .cursorrules file that prevents editing of files that are not explicitly mentioned in task descriptions. The rule should clearly define the conditions under which file editing is permitted and outline the consequences for violations. Additionally, include examples of acceptable and unacceptable file edits to provide clarity. Ensure the rule is concise, easy to understand, and can be implemented effectively within the existing framework.

Create a detailed checklist to ensure that task descriptions are followed precisely at the start of each session. The checklist should include items such as: confirming the task objectives, reviewing any specific requirements or constraints, verifying the resources needed, and ensuring all team members are aligned on their roles. Additionally, include a section for noting any potential scope creep or unasked changes that may arise during the session. Format the checklist in a clear, organized manner with bullet points for easy reference.

Please insert a comment in the codebase that reminds developers to specify the exact files and functions in their task descriptions. The comment should emphasize the importance of clarity and precision in task assignments to prevent scope creep and unasked changes. Make it concise yet informative, ideally no more than three sentences, and ensure it is placed in a relevant section of the code where developers are likely to see it. The comment should also encourage open communication regarding any uncertainties related to task specifications.

Propose a detailed naming convention for tasks that effectively communicates the scope of files and functions to be edited. The convention should include specific guidelines on how to structure names, such as using prefixes or suffixes to indicate the type of task, the associated module or feature, and the priority level. Additionally, provide examples of task names that follow this convention, ensuring they are clear and easy to understand. Explain how this naming convention can help prevent scope creep and unasked changes in future projects.

Design a project guard mechanism that will monitor and alert the team whenever edits are attempted on files or functions that have not been explicitly specified in the project scope. The guard should include features such as real-time notifications, a log of attempted changes, and a review process for any unauthorized edits. Additionally, outline how this mechanism can be integrated into the existing workflow, including any necessary permissions or roles that should be established. Provide a detailed implementation plan that includes potential challenges and solutions to ensure its effectiveness.