AI Prompts for Preventing Unauthorized Code Changes

Please provide a detailed list of all code changes made during the last session. For each change, indicate whether it was part of the original request or if it was an unintended modification. Highlight any changes that were not explicitly requested, and provide a brief explanation for each unintended change, including potential impacts on the overall project. Format the response in a clear table with columns for 'Change Description,' 'Requested Task,' and 'Unintended Change Explanation.'

Please provide a detailed explanation of the changes made to [FILE_NAME] that were not part of the original task. Include the reasoning behind these changes, outlining any specific rules, logic, or considerations that influenced your decision. Additionally, discuss how these changes align with the overall project goals and any potential impacts they may have on the final outcome. Aim for a comprehensive response that covers the rationale and implications of the modifications.

Please analyze the following .cursorrules file: [PASTE CONTENT]. Confirm which rules were applied to the last task and provide a detailed list of any rules that were ignored. For each ignored rule, explain why it was not applied and suggest any potential adjustments that could ensure better compliance in future tasks. Format your response in a clear, organized manner, highlighting key findings and recommendations.

Please analyze the following task: [PASTE TASK]. Identify whether any part of this task suggests that changes outside the specified files are necessary. If so, provide a detailed explanation of your reasoning, including which aspects of the task led you to this conclusion and any potential implications of making those changes. Additionally, suggest any alternative approaches that could be taken to stay within the defined scope.

Please provide a comprehensive list of all files accessed during the last task. For each file, indicate whether any changes were made without explicit instruction. Include details such as the file name, the type of changes made, and the reasons for those changes if applicable. Format the output as a table for clarity, with columns for 'File Name,' 'Changes Made,' and 'Reason for Change'.

Please revert all changes made to files that are not specified in the task. Ensure that only the designated files remain modified, and provide a confirmation once the reversion is complete. Additionally, summarize any changes that were reverted and specify the files that were left unchanged.

Please ensure that any changes made in future tasks are strictly limited to the files I specify. Provide a clear confirmation that you understand this instruction and outline the process you will follow to adhere to this limitation. Additionally, explain how you will handle any requests for changes outside of the specified files to maintain focus and avoid unnecessary alterations.

Please clarify the intent of the following task: [PASTE TASK]. Based on your understanding, identify and list the specific files that will be impacted by this task. Additionally, provide a brief explanation of how each file will be affected and any potential implications of these changes. Ensure that your response is clear and detailed to avoid any misunderstandings.

Please identify and undo the specific changes made in [FILE_NAME] that were not part of the original task. After reverting these changes, provide a detailed summary of what was altered, including the nature of each change and its impact on the overall document. Ensure that the summary highlights any significant differences between the original and the modified versions, and format it as a clear list for easy reference.

Please apply the following task-specific rules to the current task: [LIST RULES]. Ensure that each rule is implemented correctly and confirm once the application of these rules is complete. Additionally, provide a brief summary of how each rule was applied and any adjustments made during the process.

Please confirm whether all unintended changes have been successfully reverted. Provide a detailed summary of the current state, including any changes that were made, the reasons for the reversion, and any remaining issues that need to be addressed. Additionally, outline any next steps that may be necessary to ensure stability moving forward.

Please validate the application of rules to the task at hand. Identify and list only the specified rules that should have been applied, and then check for any deviations from these rules. For each deviation found, provide a brief description of the nature of the deviation and its potential impact on the task. Ensure that your response is clear and structured, summarizing the findings in a way that can be easily reviewed.

Please cross-check the current state of [FILE_NAME] with its previous version. I need a detailed comparison that highlights all the changes made, including additions, deletions, and modifications. Confirm that only the intended changes are present and provide a summary of any unintended alterations found. Additionally, include recommendations for addressing any discrepancies you identify.

Please conduct a comprehensive code integrity check to identify any unauthorized changes in the codebase. Provide a detailed report that outlines any discrepancies or issues found, including the specific files affected and the nature of the changes. Additionally, suggest potential remediation steps for any identified issues to restore the integrity of the code. Ensure the report is clear and structured for easy understanding.

Please verify that the task related to [SPECIFIC TASK OR FEATURE] has been completed according to the specified requirements. Ensure that the changes made do not negatively impact other parts of the codebase. Provide a detailed confirmation report that includes any observations or issues encountered during the verification process, along with suggestions for improvements if necessary.

Please create a new rule for my .cursorrules file that prevents unauthorized changes based on recent issues I have encountered. The rule should specify the conditions under which changes are allowed and outline the consequences for unauthorized modifications. Include any relevant parameters or settings that need to be configured to ensure the rule is effective. Provide the exact text of the rule formatted for easy insertion into the .cursorrules file.

Create a code comment template that outlines the specific files that can be modified during a task. The template should include sections for the task name, a brief description of the changes allowed, and a list of the files that can be altered. Additionally, include a section for the rationale behind these changes and any relevant notes for future reference. Format the template clearly so that it can be easily filled out by developers.

Please create a detailed checklist for opening a new session that ensures only the specified files are modified. The checklist should include steps such as verifying the correct files are selected, confirming that no unintended files are open, and outlining any necessary pre-session configurations. Additionally, include reminders for saving current work and backing up files before starting the session. Format the checklist in a clear, easy-to-follow manner, with each step numbered for clarity.

Suggest a naming convention for tasks that clearly indicates the scope of allowed changes. The convention should include specific prefixes or suffixes that denote the type of changes permitted, such as 'Modify', 'Review', or 'Update'. Provide at least five examples of task names using this convention, and explain the rationale behind each choice to ensure clarity and consistency in task management.

Create a project guard mechanism that monitors changes made to a project and alerts me when modifications occur outside the specified scope. Detail the components of this system, including how it identifies unauthorized changes, the criteria for determining what constitutes the specified scope, and the method of alerting me (e.g., notifications, reports). Additionally, explain how this mechanism can prevent recurrence of unauthorized changes and suggest best practices for implementing it effectively in a project management environment.