AI Prompts for Preventing Code Overwrites in Claude

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 may have been violated in the recent changes I made. Provide a brief explanation for each identified violation and suggest how I can rectify these issues to ensure compliance moving forward.

Please provide a detailed list of all the changes made in the last coding session. For each change, specify the file or section of code that was modified and describe the nature of the change. Highlight any modifications that could potentially impact existing working code, and explain how these changes might affect functionality or introduce bugs. Organize the information in a clear format, such as a bullet-point list, to enhance readability.

Please analyze the code changes made during the last feature addition. Identify any code that was deleted or overwritten, and provide a detailed explanation for each change. Include the specific lines of code affected, the reasons behind the deletions or overwrites, and how these changes contribute to the overall functionality of the feature. Additionally, discuss any potential impacts these changes may have on existing functionality or performance.

Please review the process of adding a new feature to the codebase. Explain each step in detail, including the specific changes made and the rationale behind them. Identify any areas where existing code may have been unintentionally altered during this process, and provide examples of how these changes could impact the overall functionality. Additionally, suggest any potential solutions or best practices to avoid similar issues in the future.

Explain how the fixed context window may have impacted your ability to keep track of previous code when integrating a new feature. Discuss specific instances where the limitations of the context window hindered your understanding of the existing codebase. Provide examples of how this loss of context affected your coding process, including any errors or misunderstandings that arose as a result. Additionally, suggest potential strategies or solutions to mitigate these issues in future development.

Please review the codebase for [PROJECT NAME] and identify any changes made that are unnecessary for the new feature implementation. List these changes along with a brief explanation of why they are not needed. After identifying them, provide the steps to revert these changes and restore the original code to ensure the functionality remains intact. Include any potential impacts of these reverts on the overall project and suggest best practices to avoid similar issues in the future.

Identify the specific lines of code that have been overwritten in the provided codebase. Restore these lines to their original state, ensuring that they are functioning correctly. Additionally, provide a brief explanation of what each line does and any potential impact on the overall functionality of the code. Format your response to include the original lines, the restored lines, and the explanations clearly labeled for easy reference.

Explain the reasoning behind overwriting the existing code in your project. Detail the specific changes made and the rationale for those changes, including any benefits or improvements expected from the new feature. If the overwrite was a mistake, provide a corrected version of the code that restores the previous functionality while ensuring that the new feature integrates seamlessly with the existing system. Additionally, outline any potential issues that may arise from the integration and how they can be addressed.

Identify any functions that have been deleted from the codebase. Restore these functions and ensure they are fully functional with the new feature that has been implemented. Provide a summary of the restored functions, including their purpose and any dependencies they may have. Additionally, run tests to confirm that the restored functions work correctly and do not introduce any new issues.

Please explain how the new feature, [FEATURE NAME], should integrate with the existing codebase. Detail the specific areas of the current code that will be affected and outline the necessary adjustments to ensure compatibility. Include any potential conflicts that may arise and how to resolve them without overwriting existing functionality. Additionally, provide examples of code snippets that illustrate the integration process and any testing strategies to confirm that the integration works as intended.

Please run a comprehensive suite of tests on the restored code for [PROJECT NAME]. Ensure that all relevant unit tests, integration tests, and end-to-end tests are executed to verify that the code functions as intended. Provide a detailed report of the test results, including any errors or failures encountered, along with a summary of the overall success rate of the tests. Additionally, highlight any areas that may require further attention or debugging based on the results.

Please reproduce the original scenario that caused the issue with the new feature. Verify that the feature functions as intended and does not negatively impact any existing code. Document any discrepancies or unexpected behaviors you observe during testing. Additionally, provide a summary of your findings, including whether the feature is stable and ready for deployment.

Please provide a detailed list of all the changes made to resolve the issue. For each change, confirm whether it was necessary and explain why it was effective in fixing the problem. Additionally, include any relevant context or examples that illustrate the impact of these changes on the overall functionality of the code. Aim for a comprehensive overview that can serve as a reference for future troubleshooting.

Please review the entire codebase for [PROJECT NAME] to ensure that no parts have been unintentionally altered during recent changes. Provide a detailed report on the integrity of the code, highlighting any discrepancies or issues found. Include specific sections of the code that were affected, the nature of the changes, and recommendations for restoring integrity if necessary. Additionally, summarize the overall health of the codebase and any potential risks that may arise from the current state.

Please review the changes made to the project and verify adherence to the CLAUDE.md guidelines. Provide a detailed analysis of each rule to ensure compliance, and identify any potential violations or areas of concern. Summarize your findings in a report format, highlighting any specific sections of the changes that either meet or do not meet the CLAUDE.md standards. Include recommendations for any necessary adjustments to ensure full compliance.

Draft a new rule for the CLAUDE.md document to prevent recurrence of incidents similar to the one that occurred. The rule should clearly outline the specific actions to be taken when encountering potential issues, including guidelines for code review, testing protocols, and communication procedures among team members. Ensure that the rule is concise yet comprehensive, and provide the exact text that can be directly added to the CLAUDE.md file. Additionally, include any relevant examples or scenarios that illustrate the importance of this rule in maintaining code integrity.

Create a detailed checklist for integrating new features into an existing codebase while ensuring that no current functionality is overwritten. The checklist should include steps such as: reviewing the current code structure, identifying dependencies, creating a backup of the existing code, testing new features in a separate branch, and conducting thorough code reviews. Additionally, include guidelines for documenting changes and a plan for regression testing to confirm that existing features remain intact. Format the checklist in a clear, numbered list for easy reference.

Please provide detailed comments to be added above critical functions in my code that warn against overwriting. The comments should clearly explain the importance of not altering these functions and outline the potential consequences of doing so. Include specific examples of what could go wrong if these functions are overwritten, and format the comments in a way that is easy to read and understand. Ensure that the comments are concise yet informative, and provide the exact text that should be used for each comment.

Please create a reminder message that I can paste at the beginning of each coding session to prevent accidental code overwrites. The reminder should emphasize the importance of saving current work and making backups before starting any new changes. Include a clear instruction to double-check that the correct files are open and that any unsaved changes are saved. Format the reminder in a concise, easy-to-read manner, ideally as a bullet-point list.

Please draft a detailed code review protocol that outlines the steps to be taken before finalizing any code changes. Include sections on the criteria for review, the roles and responsibilities of team members involved in the review process, and the tools or methods to be used for tracking changes. Additionally, specify the timeline for reviews, how feedback should be documented and communicated, and any best practices to ensure high-quality code is maintained. Format this as a comprehensive document that can be easily followed by the development team.