AI Prompts for Preventing Reversion of Approved Changes

Please provide a detailed list of all recent changes made in the project tree. For each change, include the date it was made, a brief description of the modification, and the specific files or components affected. Additionally, highlight any changes that were reverted unexpectedly, explaining the reason for the reversion if known. Format the information in a clear table for easy reference.

Please review the following .cursorrules file content: [PASTE CONTENT]. Analyze the rules within the file and identify any specific rule that could be responsible for causing the reversion of approved changes. Provide a detailed explanation of how each identified rule may impact the changes, and suggest any modifications or adjustments that could prevent this issue from occurring in the future. Conclude with a summary of your findings and recommendations for best practices in managing these rules.

Please analyze the session history for any actions that may have led to the reversion of changes. Focus on identifying specific events, timestamps, and user actions that could have contributed to this issue. Summarize your findings in a clear and concise report, highlighting any patterns or anomalies you observe. Include recommendations for preventing similar issues in the future based on your analysis.

Please provide a comprehensive list of all currently open files in the project. For each file, indicate whether there are any unsaved changes present and highlight any potential conflicts these changes may have with the approved changes. Additionally, summarize the nature of the unsaved changes and suggest possible actions to resolve any conflicts identified. Format the response in a clear table with columns for file name, unsaved changes status, conflict details, and recommended actions.

Please provide a comprehensive list of all AI suggestions made during this session. For each suggestion, indicate whether it was accepted or reverted. Additionally, include any relevant context or reasoning behind the decisions made for each suggestion. Format the output in a clear table with columns for the suggestion, its status (accepted or reverted), and any notes that may help in understanding the changes.

Identify the specific change that was reverted in the project. Please restore this change to its approved state and provide a detailed explanation of the reasons behind the reversion. Additionally, outline any potential impacts this change may have on the project moving forward, and suggest any necessary steps to prevent similar issues in the future.

Please analyze the rules defined in the .cursorrules file to identify any that may be causing the reversion issue. Once you locate the conflicting rule, provide a detailed explanation of the modifications you will make to prevent this behavior. Include the rationale behind each change, how it addresses the conflict, and any potential impacts on the overall functionality. Format your response in a clear, structured manner, and ensure it is comprehensive enough for someone unfamiliar with the original context to understand.

Please describe a mechanism to lock changes once they have been approved. Include details on how this mechanism will function to prevent any future reversion of these changes during subsequent sessions. Outline the steps involved in the approval process, the criteria for locking changes, and any safeguards that will be put in place to maintain the integrity of the approved changes. Additionally, explain how users will be notified of locked changes and the process for unlocking if necessary.

Please disable the auto-revert feature if it is currently enabled. Explain how this feature has been impacting the approved changes, specifically detailing any instances where changes were reverted unexpectedly and how that affected the overall project. Additionally, provide recommendations on how to manage changes moving forward to prevent similar issues from occurring. Include any relevant considerations for team members who may be affected by this change.

Identify any instances where the AI may have misinterpreted instructions that led to the need for reversion. Provide a detailed analysis of the misunderstanding, including specific examples of the misinterpretation. Then, outline the correct behavior or response that should have been generated instead. Ensure that your documentation is clear and structured, so it can be easily referenced for future improvements.

Reapply the previously reverted change in the system and confirm that it persists across multiple sessions. Please provide a detailed report that includes the steps taken to reapply the change, any relevant screenshots or logs that demonstrate the change is still effective, and a summary of how the change impacts the overall functionality. Additionally, outline any potential issues that could arise if the change does not persist and suggest possible solutions.

Please run a series of tests to verify that the modified rules in the configuration file [FILE NAME] are effectively preventing any reversion of changes. Document the test cases you used, including the specific scenarios and conditions tested. Provide a summary of the results for each test, indicating whether the modified rules passed or failed, along with any relevant observations or recommendations for adjustments. Format the results in a clear and organized manner, highlighting any areas that may need further attention.

Please simulate the scenario that originally led to the reversion of changes in the project. Describe the specific conditions and actions that triggered the issue, and then confirm whether the problem still exists. Provide detailed before-and-after evidence, including any relevant data or screenshots that illustrate the resolution of the issue. Summarize your findings and any additional insights you may have regarding the changes made.

Please validate the lock mechanism implemented for approved changes. Test its functionality to ensure that it effectively prevents any reversion of these changes. Provide a detailed report on the results, including any scenarios where the mechanism was tested, the outcomes of each test, and any issues encountered during the validation process. Additionally, include recommendations for improvements if any weaknesses are identified.

Please explain your current understanding of the approved changes made to the project. I would like you to summarize the key modifications, the reasons behind these changes, and how they impact the overall objectives. Additionally, please highlight any potential challenges or considerations that may arise from these changes. Your response should be clear and concise, ideally in three to five sentences.

Please create a new rule for .cursorrules that prevents the reversion of approved changes. The rule should include specific conditions under which changes can be reverted and outline the consequences for unauthorized reversion attempts. Ensure that the rule is clear and concise, providing the exact text that should be added to the rules file. Additionally, explain how this rule will help maintain the integrity of approved changes and prevent future issues.

Create a comprehensive checklist to be used at the beginning of each session to prevent the reversion of approved changes. The checklist should include specific items such as verifying the current version of the project, confirming that all recent changes have been documented, ensuring that team members are aware of the approved changes, and checking for any pending updates that may affect the project. Format the checklist in bullet points for easy reference, and aim for at least 8 to 10 items to cover all necessary aspects.

Please generate a comment to be placed above the affected code that warns AI assistants against reverting approved changes. The comment should clearly state the importance of maintaining these changes and provide context for why they should not be altered. Ensure the comment is concise yet informative, ideally no more than three sentences long, and formatted in a way that is easily readable for developers. The final comment text should be: '[INSERT COMMENT TEXT HERE]'. Make sure to use a professional tone suitable for a codebase.

Help me establish a comprehensive project convention for managing approved changes to prevent their reversion. The convention should include guidelines on how changes are documented, the process for reviewing and approving changes, and the roles and responsibilities of team members involved in this process. Additionally, outline strategies for communicating these changes to all stakeholders and methods for monitoring compliance with the convention. Format the response as a detailed document that can be shared with the project team.

Please create a comprehensive set of guidelines for interacting with AI systems to ensure that all approved changes are consistently respected. The guidelines should cover best practices for communication, including how to phrase requests clearly and concisely, the importance of providing context for changes, and methods for confirming that changes have been implemented correctly. Additionally, include examples of effective interactions and common pitfalls to avoid. Format the guidelines in a numbered list for easy reference, and aim for a total length of at least 300 words.