AI Prompts for Identifying Cascade Breaks in Code

Please provide a detailed list of all recent changes made in the project. For each change, include the following information: the timestamp of when the change was made, a brief description of the change, and the specific files that were affected. Organize the information in a clear format, such as a table, to make it easy to read and understand. Ensure that the list covers changes made within the last [TIME FRAME] and highlight any significant updates or modifications.

Analyze the project and identify which files or features are currently broken. Provide a detailed list of these affected files, including their names, locations within the project structure, and a brief description of the issues associated with each file. Additionally, include any relevant error messages or symptoms that indicate the problems. Format the output as a structured report that can be easily reviewed and used for troubleshooting.

Analyze the recent changes made to the project and identify any dependency issues that may have arisen as a result. List any conflicts found, detailing which dependencies are affected and how they conflict with each other. Include information on the versions involved and any potential impact these issues could have on the overall functionality of the project. Provide recommendations for resolving these conflicts to ensure smooth operation.

Please review the error logs for any entries related to the recent changes made in the system. Identify and highlight any relevant errors that may indicate issues or failures resulting from these changes. Provide a summary of the findings, including the error codes, descriptions, and any potential impact on the system's functionality. Additionally, suggest possible next steps for troubleshooting or resolving the identified errors.

Please analyze the database schema for [DATABASE NAME] to identify any inconsistencies or errors that may have been introduced by recent changes. Focus on key areas such as table relationships, data types, and constraints. Provide a detailed report highlighting any issues found, including specific tables or fields affected, and suggest potential solutions or improvements. The report should be structured in sections for clarity, with a summary of the most critical findings at the beginning.

Revert the changes made to [FILE_NAME] and check if the issue still occurs. After reverting, please provide a detailed analysis of the outcome, including any error messages or unexpected behavior that arises. Additionally, describe the steps taken during the reversion process and any observations that could help in diagnosing the root cause of the problem. If the issue persists, suggest potential next steps for further investigation.

Identify and resolve any dependency conflicts that have been previously flagged in the project. Please provide a detailed list of each conflict, including the specific dependencies involved and the reasons for the conflicts. Outline the steps taken to resolve each issue, ensuring to include any changes made to the configuration files or code. Additionally, summarize the overall impact of these resolutions on the project's functionality and stability.

Please review the database schema provided and identify any issues or inconsistencies. For each issue found, explain the nature of the problem and the specific corrections that need to be made. Include details such as the affected tables, columns, and any changes to data types or relationships. After making the corrections, summarize the final schema and highlight how these changes improve the overall structure and integrity of the database.

Identify the affected files that are experiencing breaking changes in the project. Once identified, apply the necessary patches to each file to resolve these issues. After applying the patches, confirm their effectiveness by running tests to ensure that the changes have successfully fixed the problems without introducing new issues. Provide a summary of the changes made and any remaining concerns that need to be addressed.

Please conduct a thorough test of the authentication features to verify that they are functioning correctly after the recent changes. Outline the specific aspects of authentication that need to be tested, such as login, logout, password reset, and user registration. For each feature, document any issues encountered, including error messages, unexpected behaviors, or performance concerns. Provide a detailed report summarizing your findings, including steps to reproduce any issues and suggestions for potential fixes.

Please run the full test suite to verify that all features of the application are functioning correctly. After completing the tests, provide a detailed summary of the test results, including the number of tests passed, failed, and any that were skipped. Additionally, include information on any errors or issues encountered during the testing process, along with suggestions for resolving them. Format the summary in a clear and organized manner for easy review.

Please analyze the application after the recent fix to identify any silent failures that may have occurred. Provide a detailed report on any issues detected, including the nature of the failures, their potential impact on application performance, and any relevant error messages or logs. Additionally, suggest possible solutions or next steps to address these failures. Ensure the report is structured clearly, with sections for findings, impact assessment, and recommendations.

Please validate all database operations for [DATABASE NAME] to ensure they are executing correctly. Provide a detailed report that includes the status of each operation, indicating whether it was successful or failed, along with any error messages if applicable. Additionally, summarize any discrepancies found during the validation process and suggest potential solutions for any failed operations. The report should be structured clearly, with sections for successful operations, failed operations, and recommendations.

Please verify the integrity of all dependencies related to [PROJECT NAME]. Check that each dependency is correctly installed and functioning as expected. Provide a detailed status report that includes: the name of each dependency, its current version, whether it is functioning properly, and any issues or warnings encountered during the verification process. Format the report in a clear, organized manner, and include recommendations for any dependencies that require attention or reinstallation.

Please verify the functionality of the user interface (UI) for [APPLICATION NAME] and ensure that all elements are working as intended. Test each feature and interaction, looking for any glitches or discrepancies in performance. If you encounter any issues, document them in detail, specifying the nature of the problem, the steps to reproduce it, and any relevant screenshots or error messages. Additionally, provide suggestions for potential fixes or improvements based on your findings.

Please draft a new rule for the CLAUDE.md file aimed at preventing cascade breaks similar to the recent issue. The rule should clearly outline the conditions that trigger a cascade break and specify the actions to take to avoid them. Include examples of scenarios where this rule would apply, and ensure the language is precise and actionable. Format the rule in a way that can be easily integrated into the existing documentation, and provide the exact text to be added.

Please add detailed comments to the codebase that explain the changes made and the reasoning behind each modification. For each section of code, include a brief description of its purpose, any important variables or functions, and how the changes improve functionality or address specific issues. Additionally, provide examples of the types of comments you would include, ensuring they are clear and informative for future developers reviewing the code. Aim for a thorough explanation that enhances understanding and maintainability of the code.

Create a comprehensive checklist to follow before committing changes to a codebase. The checklist should include steps to verify that no unrelated features are impacted by the changes. Cover aspects such as reviewing the scope of changes, running relevant tests, ensuring all dependencies are updated, and confirming that documentation is updated accordingly. Format the checklist in a clear, numbered list for easy reference, and include any specific considerations for different types of changes or features.

Help me establish clear naming conventions for files and variables to minimize confusion in our project. Please provide a detailed list of these conventions, including examples for different types of files (e.g., documents, images, scripts) and variables (e.g., constants, functions, classes). Additionally, explain the rationale behind each convention and how it contributes to better organization and readability. Aim for a comprehensive guide that can be easily referenced by the team.

Help me design and implement project guards that will effectively catch potential cascade breaks early in the development process. Detail the types of guards that can be utilized, including their purpose and how they function within the project. Provide a step-by-step guide on how to implement these guards, including any necessary code snippets or configurations. Additionally, explain how to test the effectiveness of these guards to ensure they are functioning as intended and preventing issues before they arise.