AI Prompts for Preventing Code Overwrites

Please provide a detailed summary of the changes made in the last coding session. Highlight any code that was removed or overwritten, and for each change, explain the rationale behind it. Include information on how these modifications improve the overall functionality, address specific issues, or enhance performance. Additionally, if applicable, mention any potential impacts these changes may have on the existing codebase or future development.

Please provide a detailed report of all the files modified in the last build. For each file, include the following information: the specific changes made, the rationale behind those changes, and any potential impact those changes may have on the overall functionality of the project. Additionally, summarize any issues that arose during the modification process and how they were addressed. Format this report in a clear, organized manner for easy reference.

Please analyze the impact of adding the new feature [FEATURE NAME] on the existing codebase. Identify all the specific sections of code that were modified and provide a detailed explanation of each change, including the purpose of the modification and how it relates to the new feature. Additionally, discuss any potential implications these changes may have on the overall functionality and performance of the application. Format your response in a structured way, highlighting each code change and its rationale.

Please provide a detailed review of the error logs from the last build attempt. Focus specifically on identifying and highlighting any errors that are related to code overwriting or removal. Additionally, summarize the potential causes of these errors and suggest possible solutions or next steps to address them. Format the response in a clear and organized manner, including any relevant timestamps or error codes for further analysis.

Please provide a detailed explanation of any code reversions that occurred during the last session. For each reversion, include the specific changes that were made, the reasons behind the decision to revert them, and any potential impacts on the overall project. Additionally, outline any lessons learned from these reversions that could help prevent similar issues in the future. Format your response as a structured report with clear headings for each reversion.

Please restore the overwritten code in the section labeled [SPECIFIC CODE SECTION]. Provide the previous version of the code and include a detailed explanation of the changes that led to it being overwritten. Additionally, discuss the potential impact of these changes on the overall functionality of the project and any steps that can be taken to prevent similar issues in the future. Format your response clearly, separating the restored code and the explanation for easy reference.

Identify the code that was mistakenly removed from the project. Provide a detailed explanation of why this code was important and the potential impact of its removal on the overall functionality. Additionally, restore the code to its original state and outline any necessary adjustments that may be required to ensure it integrates smoothly with the existing codebase. Please present this information in a clear and organized format, including code snippets where applicable.

Help me fix the integration of [FEATURE NAME] into the existing codebase. Ensure that no existing functionality is disrupted or overwritten during the integration process. Identify any potential integration errors and provide detailed steps to correct them. Additionally, suggest best practices for maintaining code integrity while adding new features. Format your response as a checklist that I can follow to ensure a smooth integration.

Identify the cause of the build failure that is related to code overwriting in the project. Analyze the codebase to pinpoint the specific lines or components that are causing the issue. Once identified, provide a step-by-step solution to fix the problem, including any necessary code changes and the rationale behind them. Additionally, explain how to prevent similar build failures in the future, focusing on best practices for code management and version control.

Identify the reasons behind the unnecessary reversion of approved changes in the codebase. Provide a detailed explanation of the circumstances that led to these reverts, including any specific triggers or miscommunications. After analyzing the causes, outline a step-by-step plan to correct these changes and prevent similar issues from occurring in the future. Ensure that the solution includes recommendations for improving the approval process and communication among team members to enhance code stability.

Please display the restored code sections for [PROJECT NAME] and confirm that they are functioning as expected. Include a brief explanation of how you verified that there are no overwriting issues. Additionally, provide any relevant error messages or warnings that may have appeared during the restoration process. Finally, summarize any changes made to ensure the code operates correctly.

Please validate the addition of the new feature [FEATURE NAME] by running a comprehensive set of tests. Ensure that all existing functionality remains intact and is not adversely affected by this new feature. Document any issues or discrepancies that arise during testing and provide a summary of the results, including any necessary recommendations for adjustments or fixes. Additionally, outline the specific areas of the codebase that were tested and confirm that all relevant test cases were executed.

Please run the build process and confirm that it completes successfully. Ensure that there are no overwriting errors during the process. Provide a detailed report on the build status, including any warnings or issues encountered, and indicate whether the build was successful or if further action is needed.

Please generate a detailed change log for the last session of code modifications. Include a summary of all changes made, specifying what was added, modified, or deleted. Confirm that no previous code was overwritten and highlight any potential issues or discrepancies that may need attention. Format the log in a clear and organized manner, making it easy to review each change and its implications.

Please conduct a comprehensive stability test of the application. Verify that all features are functioning as intended and that there are no issues with code overwriting. Provide a detailed report that includes any bugs or stability concerns identified during testing, along with recommendations for improvements. Additionally, outline the steps taken during the testing process and the results for each feature tested.

Please draft a new rule for CLAUDE.md that aims to prevent code overwriting based on the recent issue encountered. The rule should clearly outline the conditions under which code can be modified and specify the necessary precautions to take before making changes. Include any relevant examples or scenarios that illustrate the importance of this rule, and format the text in a way that can be directly added to the CLAUDE.md document. Ensure that the language is clear and concise, making it easy for developers to understand and follow.

Please provide a detailed comment that should be inserted above critical functions in the code to warn against overwriting. The comment should clearly explain the importance of these functions and the potential consequences of making changes to them. Ensure the comment is concise yet informative, ideally no longer than three sentences. Format the comment as a code snippet so it can be easily copied and pasted into the codebase.

Create a comprehensive checklist for starting coding sessions that focuses on preventing code overwriting. The checklist should include specific steps such as ensuring version control is set up, confirming that all team members have the latest code updates, and establishing a protocol for saving changes. Additionally, include reminders for regular backups and reviewing recent commits before starting new work. Format the checklist in bullet points for easy reference.

Help me design a method to lock critical sections of code to prevent them from being overwritten. Outline the specific implementation steps required to achieve this, including any necessary code snippets, configuration settings, and best practices for ensuring the integrity of the locked code. Additionally, explain how to test the locking mechanism to confirm it is functioning as intended. Provide examples of scenarios where this method would be particularly beneficial.

Develop a comprehensive protocol for integrating new features into existing software systems while ensuring that current code remains intact. The protocol should include specific steps for assessing the impact of new features, guidelines for testing and validation, and strategies for version control. Additionally, outline best practices for documentation and communication among team members during the integration process. Ensure that the protocol is structured in a clear format, with sections for each stage of the integration, and provide examples where applicable.