AI Prompts for Preventing Reversion of Approved Changes

Please review the following CLAUDE.md file content: [PASTE CONTENT]. Confirm your understanding of each rule outlined in the document. Additionally, identify any specific rules that apply to the recent changes I have reverted and provide a brief explanation of how each rule relates to those changes. Summarize your findings in a structured format, highlighting any compliance issues or areas for improvement.

Please provide a comprehensive list of all the changes made during the last session. For each change, indicate whether it was reverted or approved, and if any changes were reverted, explain the reasons behind those decisions. Additionally, include any relevant context that might help understand the impact of these changes on the overall project. Format your response in a clear, organized manner to facilitate easy review.

Please summarize the change history for the files modified in the project. Include a detailed account of each change made, highlighting any discrepancies between the approved changes and the actions taken. For each discrepancy, provide context on why the change was made and its potential impact on the project. Format the summary in a clear, organized manner, with sections for each file and a conclusion that outlines the overall compliance with the approved changes.

Analyze the pattern of changes that have been reverted in the project. Identify any common reasons or rules that may have influenced these reversion decisions. Provide a detailed explanation of the factors that contributed to the need for reversion, including specific examples of changes that were reverted and the context surrounding those decisions. Additionally, summarize any trends or insights that can be drawn from this analysis to inform future change management practices.

Please restate the task that was assigned to you before the changes were reverted. Confirm your understanding of the task and identify any potential misunderstandings that may have occurred. Additionally, provide a brief summary of the key objectives and expected outcomes of the task to ensure clarity moving forward.

Reapply the changes that were previously reverted in the last session. Make sure to align these changes with the guidelines outlined in the CLAUDE.md document. For each change, provide a detailed explanation of the rationale behind it, the expected impact on the overall project, and any potential challenges that may arise from reapplying these changes. Format your response as a step-by-step guide, clearly indicating each change and its significance in the context of the project.

Identify any misinterpretations of the CLAUDE.md rules that contributed to the reversion of changes. Provide a detailed analysis of each misinterpretation, explaining why it was incorrect and how it deviated from the intended guidelines. After addressing the misinterpretations, outline the steps necessary to correctly reapply the changes in accordance with the CLAUDE.md rules. Ensure that your response is structured clearly, with each misinterpretation and correction presented in a separate section for clarity.

Please review the following approved change that was reverted: [PASTE CHANGE]. Explain the reasons behind the reversion and provide a detailed analysis of its impact. After that, please implement the necessary adjustments to reinstate the change effectively. Ensure that the final output includes a summary of the steps taken to fix the issue and any potential implications for future changes.

Adjust the application of the CLAUDE.md rules to ensure that approved changes are not reverted. Provide a detailed explanation of the specific modifications you implemented to achieve this. Include the rationale behind each adjustment, how it impacts the overall rule application, and any potential implications for future changes. Format your response in a structured manner with clear headings for each adjustment made, ensuring that it is easy to follow and understand.

Identify any conflicts between the approved changes and the current actions taken in the project. Provide a detailed analysis of each conflict, explaining how it arose and the implications it has on the overall project. Then, outline the steps taken to resolve these conflicts, ensuring that all approved changes remain intact and functional. Finally, confirm that the final state of the project reflects these changes accurately and summarize any adjustments made during the resolution process.

Please verify that the re-applied changes in the project remain intact. List all the files that were affected by these changes and confirm that no further reversion has occurred since the changes were made. Additionally, provide a brief summary of the changes that were re-applied and any potential implications for the project moving forward.

Please execute a series of tests on the files where changes have been reapplied. I need a detailed report of the test results, including any errors or failures encountered during the testing process. Additionally, provide an analysis of whether the changes are stable and functioning as intended. Include recommendations for any further actions if issues are found, and summarize the overall stability of the changes in a clear format.

Please recreate the original scenario that led to the reversion of changes. Describe the specific conditions and inputs that were present during that scenario. After reproducing the scenario, verify that the changes now persist without any issues. Provide a detailed report on your findings, including any discrepancies or confirmations of the changes working as intended.

Please provide a detailed summary of the changes made in the project, including specific modifications and their intended outcomes. For each change, confirm its current status, indicating whether it is stable and not subject to reversion. Additionally, outline any potential risks or considerations that may affect the stability of these changes in the future. Format your response in a clear, structured manner, using bullet points for each change to enhance readability.

Please validate that all changes made adhere to the CLAUDE.md rules. Review each change carefully and confirm that there are no violations that could lead to a reversion of the changes. Provide a summary of any potential issues found, including specific rules that may have been violated and suggestions for how to correct them. Ensure that your response is clear and structured, detailing the compliance status of each change.

Draft a new rule for the CLAUDE.md document that aims to prevent the reversion of approved changes. The rule should clearly outline the process for handling approved changes, including the circumstances under which they can be reverted and the necessary approvals required for such actions. Additionally, include any relevant guidelines or best practices that should be followed to ensure transparency and accountability in the change management process. Format the rule in a clear, concise manner, suitable for inclusion in the existing CLAUDE.md document.

Create a detailed 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 code, confirming that all recent changes have been documented, ensuring that any automated tests are up to date and passing, and reviewing any pending pull requests that might affect the approved changes. Additionally, include a section for team members to sign off on the checklist to ensure accountability. Format the checklist in a clear and organized manner for easy reference.

Please insert a comment above the affected function that warns AI assistants not to revert approved changes. The comment should clearly state the importance of maintaining approved modifications and provide a brief explanation of why reverting these changes could lead to issues. Ensure the comment is concise yet informative, ideally no more than three sentences long. Format the comment in a way that is easily readable and follows standard coding conventions.

Draft a comprehensive protocol for managing approved changes to ensure they are not reverted in the future. The protocol should include the following sections: the purpose of the protocol, the process for documenting approved changes, the steps for communicating these changes to the relevant teams, and the methods for monitoring compliance. Additionally, outline the roles and responsibilities of team members involved in this process. Format the protocol as a clear and concise document suitable for inclusion in CLAUDE.md, ensuring it is easy to follow and implement.

Draft a session opener that emphasizes the significance of maintaining approved changes in our processes. The opener should highlight the potential risks of deviating from these changes, such as project delays or quality issues. Include a motivational statement that encourages the team to stay committed to the approved changes and to communicate any concerns or suggestions for improvement. Aim for a length of 3 to 5 sentences, ensuring it sets a positive and focused tone for the session.