AI Prompts for Preventing Unwanted Code Refactoring

Please provide a detailed list of the recent changes made to the codebase. Specifically, highlight any modifications that were not included in my last request. For each unapproved change, include a brief description of what was altered, the reason for the change if available, and any potential impact it may have on the overall project. Format this information in a clear and organized manner, so I can easily review and address any discrepancies.

Please provide a detailed summary of the tasks processed in the last [TIME FRAME], highlighting those that involved code refactoring. For each task, include the task name, the date it was completed, a brief description of the changes made during the refactoring process, and any relevant outcomes or impacts on the project. Structure the information in a clear format, such as a table or bullet points, to make it easy to review.

Please compare the original code provided below with the current version. Here is the original code: [PASTE ORIGINAL CODE]. Identify and list all differences between the two versions, highlighting changes in functionality, structure, and any modifications in comments or documentation. Additionally, provide a brief explanation of the impact of these differences on the overall performance and readability of the code.

Please review the logs of my recent refactoring activities. Identify and summarize the changes that were made without explicit requests, highlighting the rationale behind each change. Additionally, provide insights on how these changes may impact the overall project and any potential areas for further improvement. Format your response in a structured manner, including sections for each change, its purpose, and its implications.

Please provide a detailed report analyzing the changes made to each component in the project. Include specific information about what modifications were made, the reasons behind these changes, and any unexpected alterations that may have occurred. Additionally, categorize the changes into sections such as critical, minor, and cosmetic, and provide a summary of the overall impact these changes may have on the project. Format the report clearly, using bullet points for easy readability.

Please revert the changes made to the code that were not part of my original request. Clearly identify which changes are being undone and provide a brief explanation of why they were not included in my instructions. Once the reversion is complete, confirm that the code has been restored to its previous state and summarize the current status of the code.

Please lock the following sections of code to prevent any future modifications: [SPECIFY CODE SECTIONS]. Ensure that the locking mechanism is clearly documented, including the reasons for locking each section and any potential impacts on the overall codebase. Additionally, provide guidance on how to request changes to these locked sections in the future, including the approval process and any necessary documentation. Format your response as a detailed report that can be shared with the development team.

Please restrict the refactoring process to only the following components: [LIST OF COMPONENTS]. Ensure that no other parts of the codebase are altered during this process. Provide a detailed explanation of the changes made to each specified component and the rationale behind them. Additionally, outline any potential impacts these changes may have on the overall functionality of the codebase.

Please revert the code to the previous stable version. Verify that no unapproved changes are included in this version. Provide a summary of the changes that were made in the current version compared to the previous stable version, highlighting any potential issues or conflicts that may arise from the reversion. Additionally, outline the steps taken to ensure that the code is functioning correctly after the reversion.

Please help me clarify the task boundaries for the upcoming project. I need to define the exact scope of changes that are required, including any specific deliverables and deadlines. Outline the key areas where clarification might be necessary, and suggest questions I should ask to ensure that I fully understand the expectations. Additionally, provide a brief summary of how to communicate these boundaries effectively to the team.

Please analyze the current codebase for any unapproved changes and confirm that they have been successfully removed. Provide a detailed report that includes the number of changes identified, the specific files affected, and any discrepancies found during the review. Additionally, outline the steps taken to verify the integrity of the code and ensure compliance with the approved standards. Format the report in a clear and organized manner for easy reference.

Please validate the functionality of each component in the system. Confirm that each component operates as intended and meets the specified requirements without any unintended modifications. Provide a detailed report that includes the name of each component, its expected behavior, any discrepancies found, and suggestions for improvement if necessary. The report should be structured clearly, allowing for easy identification of components that require further attention.

Please execute a comprehensive set of regression tests to ensure that the system functions correctly following the recent changes. Focus on key functionalities such as [FUNCTIONALITY 1], [FUNCTIONALITY 2], and [FUNCTIONALITY 3]. Provide a detailed report of any issues discovered, including the steps to reproduce them, the expected behavior, and the actual behavior observed. Additionally, summarize the overall health of the system post-changes and highlight any areas that may require further attention or testing.

Please analyze the provided code for any new errors or issues that may have been introduced during the reversal process. Specifically, check for syntax errors, logical errors, and any potential runtime exceptions. Provide a detailed report that includes the line numbers of any identified issues, a brief description of each error, and suggestions for how to resolve them. Additionally, assess the overall functionality of the code to ensure it operates as intended after the reversal.

Please verify the compliance of all recent tasks completed in the last [TIME FRAME] against the specified requirements. List each task along with its completion status, and identify any deviations or discrepancies from the original requirements. For any tasks that do not comply, provide a brief explanation of the issue and suggest corrective actions to ensure alignment with the requirements. Format the results in a clear table with columns for task name, status, deviation details, and recommended actions.

Draft a new rule for CLAUDE.md that addresses unapproved refactoring to prevent recurrence of recent issues. The rule should clearly define what constitutes unapproved refactoring, outline the consequences for violating this rule, and specify the process for obtaining approval before making any changes. Ensure the language is concise and formal, and provide the exact text that can be directly included in CLAUDE.md. Aim for clarity and enforceability to ensure all team members understand the expectations.

Please develop a comprehensive set of guidelines for commenting code that clearly delineates which sections of the codebase should not be altered without explicit permission. The guidelines should include specific examples of comments that indicate critical code areas, best practices for writing these comments, and the rationale behind the need for permission before making changes. Additionally, outline the consequences of altering these sections without authorization and suggest a format for documenting these guidelines within the code itself. Aim for a detailed document that can be easily referenced by developers.

Create a detailed protocol for confirming task scopes prior to execution. The protocol should outline the steps necessary to ensure all team members agree on the task requirements, including who is responsible for final approval and how to document any changes to the scope. Additionally, specify the communication channels to be used for confirmation and the timeline for obtaining approvals. Format this protocol as a markdown document suitable for inclusion in CLAUDE.md, ensuring it is clear and easy to follow.

Propose a set of naming conventions for code that clearly indicate which sections are critical and should remain unchanged. Include guidelines for how to format these names, such as using specific prefixes or suffixes, and provide examples of both good and bad naming practices. Additionally, explain the rationale behind these conventions and how they can help prevent accidental modifications in the codebase. Aim for a comprehensive overview that can be easily referenced by developers.

Help me design a comprehensive set of project guards that will automatically flag unauthorized code changes in a software development environment. Outline the specific implementation steps required to establish these guards, including the technologies or frameworks that could be utilized. Detail how these guards will monitor code changes, the criteria for flagging unauthorized changes, and any necessary configurations or permissions needed. Additionally, provide examples of potential alerts or notifications that should be generated when a code change is flagged, and suggest best practices for maintaining the effectiveness of these guards over time.