AI Prompts for Preventing Reversion of Approved Changes

Please review the following CLAUDE.md file content: [PASTE CONTENT]. Analyze each rule outlined in the document and confirm your understanding of them. After your review, identify which specific rule should have been applied to the last task and explain how it relates to the task's requirements. Additionally, provide suggestions on how to ensure compliance with the rules in future tasks.

Please identify all instances where changes were reverted during the last session. For each instance, provide a detailed explanation of the reasons behind the reversion. Include information such as the specific changes that were reverted, the impact of those changes, and any relevant context that influenced the decision to revert. Format the response in a clear, structured list for easy reference.

Please analyze the change logs from the past [TIME PERIOD] and identify any patterns or rules that may have led to the reversion of approved changes. Focus on specific instances where changes were reverted, noting the reasons provided and any common themes that emerge. Summarize your findings in a structured report, highlighting key insights and potential recommendations for preventing future reversion issues. Include examples from the logs to support your analysis.

Please provide a detailed review of the actions taken in Cascade mode during the last session. Include a summary of each action, specifying any changes that were reverted along with the reasons for those reverts. Additionally, discuss the impact of these actions on the overall process and any lessons learned that could inform future sessions. Format your response in a structured manner with clear headings for each section.

Please evaluate the autocomplete suggestions that were made and subsequently led to reversion. Provide a detailed list of these suggestions, including the specific criteria that were used to prioritize them. For each suggestion, explain the rationale behind its selection, considering factors such as user behavior, relevance, and potential impact on user experience. Additionally, summarize any patterns or trends observed in the suggestions that may have contributed to the decision to revert them.

Temporarily disable Cascade mode for the current project. After disabling, reapply the approved changes and ensure that they are correctly implemented. Please confirm that all changes remain intact and provide a summary of any discrepancies or issues encountered during this process.

Please apply the following rule from CLAUDE.md to the current session: [SPECIFIC RULE]. Make sure to carefully analyze the current changes and ensure that no approved changes are reverted in the process. Provide a summary of how the rule impacts the session and any adjustments made to maintain the integrity of the approved changes. Additionally, outline any potential implications of applying this rule on the overall workflow.

Please lock the following approved changes: [LIST OF CHANGES]. Ensure that these changes are permanently secured and cannot be reverted in any future sessions. Provide a confirmation that these changes have been successfully locked, and outline any potential implications or considerations for maintaining these changes moving forward. Additionally, include any necessary steps to verify that the locking process has been completed effectively.

Please provide a detailed override for the autocomplete suggestions related to the following code segments: [CODE SEGMENTS]. The override should ensure that any approved changes are fully preserved and integrated into the suggestions. Additionally, explain the rationale behind each suggestion to clarify why it is appropriate for the given code segments. Format the response in a clear, structured manner, highlighting the original suggestions alongside the new overrides for comparison.

Please reapply the following changes: [LIST OF CHANGES]. After reapplying, verify that these changes remain intact and are not reverted in any subsequent operations. Provide a detailed report on the status of each change, including any discrepancies or issues encountered during the process. Additionally, outline the steps taken to ensure the changes are preserved moving forward.

Please conduct a verification check on the following files: [LIST OF FILES]. Ensure that all approved changes have been implemented accurately and are reflected in the documents. Provide a detailed report highlighting any discrepancies or missing changes, along with suggestions for corrections. Additionally, summarize the overall status of the verification process and indicate whether all changes meet the required standards.

Please verify that all actions taken in the project adhere to the rules specified in CLAUDE.md. Summarize the compliance status, detailing which rules were followed and any deviations that occurred. Include specific examples of actions taken, the corresponding rules they relate to, and any recommendations for ensuring adherence in future actions. Format the summary as a concise report with bullet points for clarity.

Please review the reversion logs for any actions taken after the last fix. I need you to confirm that no approved changes have been reverted. Provide a summary of your findings, including the dates of any reversion actions, the specific changes affected, and any relevant details that may help in understanding the context of these actions. If any reversion has occurred, please highlight the implications it may have on the current project status.

Please verify the implementation of the autocomplete adjustments. Check that all changes have been applied correctly and ensure that there are no suggestions for reversion of any approved changes. Provide a detailed report outlining any discrepancies found, including specific examples of adjustments that were not applied as intended. Additionally, confirm that the current settings align with the approved specifications and document any necessary next steps for resolution.

Please provide a detailed summary of the current session. Include a list of all changes that were made during this session, specifying which changes were approved and confirming that none of the approved changes have been reverted. Additionally, highlight any important discussions or decisions that took place during the session. Format the summary in bullet points for clarity and ensure it is concise yet comprehensive.

Based on the recent issue I encountered, please help me draft a new rule to add to my CLAUDE.md file that will prevent this problem from recurring. The rule should clearly outline the specific conditions that triggered the issue, the actions to take when these conditions are met, and any relevant guidelines or best practices to follow. Format the rule in a way that is easy to understand and implement, and provide the exact text I can copy and paste directly into my document.

Please create a detailed checklist for opening a new session that ensures approved changes are not reverted. The checklist should include steps such as verifying the current configuration settings, confirming that all recent updates have been applied, and reviewing any pending changes that could affect stability. Additionally, include a step for documenting the session's initial state and any relevant notes. Format the checklist in a clear, bullet-point style, and ensure it is comprehensive enough to be easily followed by team members.

Please review the following code segments: [CODE SEGMENTS]. For each segment, add detailed comments that clearly indicate which changes should not be reverted and explain the rationale behind these decisions. Ensure that the comments are concise yet informative, providing context for future developers. Format the comments in a way that they can be easily understood and integrated into the existing code.

Help me establish a clear naming convention for files and functions that should not have changes reverted. The convention should include specific guidelines on how to format names, such as using prefixes or suffixes to indicate their status, and should ensure consistency across the project. Please provide at least five examples of file and function names that adhere to this convention, along with explanations for why each example fits the criteria. Additionally, outline any best practices for maintaining this naming convention over time.

Help me design a project guard that will effectively monitor and prevent the reversion of approved changes in our project. Outline the key features this guard should include, such as real-time monitoring, alerts for unauthorized changes, and a rollback prevention mechanism. Additionally, provide detailed configuration settings that specify how to set up the guard, including any necessary parameters, thresholds for alerts, and integration points with existing project management tools. The final output should be a comprehensive guide that can be followed to implement this guard successfully.