AI Prompts for Restricting Unwanted Code Changes

Please provide a comprehensive list of all files and functions that were modified during the last task. For each item, indicate whether it was included in the original task description or if it represents an unintended change. Additionally, summarize the reasons for these modifications and how they may impact the overall project scope. This information will help in diagnosing any potential scope creep issues.

Please review the following task description: [PASTE TASK]. Assess whether the task was completed according to the provided description. If there were any deviations from the task requirements, detail each specific area where changes occurred, explaining the reasons for those changes and their potential impact on the overall project. Additionally, provide suggestions on how to improve adherence to task descriptions in future projects.

Please summarize all recent code modifications made to the project. For each modification, indicate whether it was a requested change or an unrequested change. Additionally, provide context for why the unrequested changes were made and how they might impact the overall project. Format the summary in a table with columns for the modification description, request status, and potential impact.

Please analyze the task execution for the project described in [TASK DESCRIPTION]. Explain how you interpreted the task and identify any assumptions you made that may have led to additional changes or scope creep. Discuss the specific elements of the task that were clear and those that were ambiguous, and how these factors influenced the final outcome. Additionally, provide recommendations on how to improve task clarity and execution in future projects to minimize unasked changes.

Please provide a comprehensive list of all components that were interacted with during the last task. For each component, indicate whether it was explicitly mentioned in the task instructions or if it was an implicit addition. Additionally, describe the role of each component in the task and any potential implications of including components that were not initially specified. This analysis should help in understanding the scope of the task and any unasked changes that may have occurred.

Please revert any changes made to files or functions that were not explicitly specified in the task description for the project [PROJECT NAME]. Provide a detailed list of the changes that were reverted, including the original state of the files or functions before the reversion. Confirm the completion of this task and ensure that all relevant stakeholders are informed of the changes. Additionally, include any potential impacts this reversion may have on the overall project timeline or deliverables.

Please create a rule that restricts future edits to only those files and functions that are explicitly mentioned in task descriptions. Ensure that this rule is clearly defined and confirm its activation status. Additionally, provide a brief overview of how this rule will help manage scope creep and unasked changes in the project. Include any necessary steps for team members to follow to adhere to this rule effectively.

Please provide a detailed plan on how to ensure that future tasks adhere strictly to their descriptions. Include specific strategies for communicating task boundaries to team members, methods for monitoring adherence to these boundaries, and steps to take if changes are requested that fall outside the original task scope. Additionally, outline how to document these boundaries clearly and effectively so that everyone involved understands their responsibilities. Aim for a comprehensive approach that can be easily implemented and reviewed.

Please identify any components in the project that were not specified in the task description. Lock these unspecified components to prevent unauthorized edits. After locking, provide a confirmation of the lock status for each component, including a brief summary of which components were locked and the reasons for their exclusion from the task description.

Please create a detailed log of all changes made during the execution of the task. The log should include the date and time of each change, a description of what was changed, who made the change, and the reason for the change if available. Format the log in a clear, organized manner, suitable for review, and ensure it captures every modification comprehensively. Once completed, provide a summary of the key changes and any potential impacts they may have on the overall project.

Please confirm that all unintended changes have been successfully reverted in the project. Provide a detailed summary of the current state, including any adjustments made, the specific elements that were reverted, and any remaining issues or concerns that need to be addressed. Additionally, outline the next steps to ensure everything is back to the original specifications and any recommendations for preventing similar issues in the future.

Please conduct a test task based on the following description: [TASK DESCRIPTION]. Confirm whether the task is being completed as specified and report any deviations or discrepancies you observe. Include details on the specific aspects that do not align with the original task description, and suggest potential solutions or adjustments to ensure compliance. Provide your findings in a structured format that highlights the key areas of concern.

Please verify the lock status of all components in the project. Confirm that any components not specified for changes remain locked and have not been altered. Provide a detailed report that includes the names of the components, their current lock status (locked or unlocked), and any relevant notes on their condition. If any components are found to be unlocked or altered, please include recommendations for how to address these issues.

Please review the change log for the project titled [PROJECT NAME] to ensure that all modifications are authorized and documented. Identify any discrepancies or unauthorized changes that may have been made, and provide a detailed summary of your findings. Include the date of each change, the nature of the modification, and any relevant comments or context that explain why a change may be considered unauthorized. Format your response as a report with clear sections for discrepancies and authorized changes.

Please validate that the rule restricting edits to specified files is being enforced within the project. Outline the specific files that are subject to this restriction and describe the methods used to monitor compliance. Include any relevant evidence, such as logs or reports, that demonstrate adherence to this rule. Additionally, provide recommendations for ensuring continued compliance and any potential areas for improvement in the enforcement process.

Draft a new rule for CLAUDE.md aimed at preventing unauthorized changes based on recent issues encountered. The rule should clearly define what constitutes unauthorized changes, outline the procedures for requesting changes, and specify the consequences for violations. Ensure the language is formal and precise, suitable for inclusion in a governance document. Provide the exact text of the rule, formatted as a clear and concise statement.

Please create a detailed checklist that outlines the essential steps to ensure all future tasks adhere strictly to their descriptions. The checklist should include items such as: verifying task requirements before starting, confirming stakeholder approval on task descriptions, setting clear deadlines, and establishing a process for documenting any changes. Additionally, include a section for regular reviews to assess adherence to the checklist and a method for addressing any deviations. Format the checklist in a clear and organized manner, suitable for team distribution.

Please add detailed comments throughout the codebase to clarify which components should not be altered without explicit instruction. For each component, include a brief explanation of its purpose, why it is critical to maintain its integrity, and any potential consequences of unauthorized changes. Additionally, provide examples of specific scenarios where modifications could lead to issues, ensuring that the comments are clear and informative for future developers. Aim for a comprehensive approach that enhances understanding and prevents scope creep.

Help me establish a set of naming conventions for files that will clearly indicate which ones are safe to edit. The conventions should include guidelines on how to categorize files based on their purpose, versioning, and status (e.g., draft, final, archived). Provide examples of naming formats that can be easily understood by team members and suggest a brief rationale for each convention to ensure clarity and consistency. Additionally, outline how these conventions can help prevent scope creep and unasked changes in future projects.

Help me design a system of project guards that will alert me when unauthorized changes are attempted in my projects. I want to understand the mechanisms these guards will use to detect changes, including any specific criteria or thresholds that will trigger an alert. Please outline the types of notifications I will receive, how these alerts will be communicated (e.g., email, dashboard notification), and any steps I should take to investigate or respond to these alerts. Additionally, provide recommendations on best practices for setting up these guards to minimize the risk of scope creep and ensure project integrity.