AI Prompts for Fixing Cascade Breaks in Codebase

Please provide a detailed report of all recent changes made to the codebase. Include the specific files that were modified, the exact lines affected, and a brief description of each change. Additionally, highlight any changes that could have a broad impact on the overall system functionality or performance. Organize the information in a clear format, such as a table, to make it easy to review and understand.

Analyze the dependencies of the changed files in the project. Identify any dependent files or modules that may be impacted by these changes and provide a detailed report on how these dependencies interact. Include information on the nature of the dependencies, potential risks associated with the changes, and any recommendations for mitigating issues that may arise. Format the findings in a structured manner, highlighting key dependencies and their relationships to the changed files.

Please review the contents of my CLAUDE.md file: [PASTE CONTENT]. Confirm whether the recent changes comply with the specified rules. Highlight any violations you find and provide a brief explanation of each issue. Additionally, suggest any necessary adjustments to ensure full compliance with the guidelines.

Trace the propagation of the error that resulted from the recent change in the codebase. Start by identifying the initial point of failure and describe how this error affected other components or modules within the system. Provide a detailed analysis of the code paths involved, including any related files or functions that were impacted, and explain how the error may have influenced the overall functionality of the application. Conclude with recommendations for preventing similar issues in the future.

Please analyze the error logs generated after the recent change in the system. I need you to identify any patterns or specific errors that suggest a cascade failure has occurred. Focus on the timestamps of the errors, the types of errors reported, and any correlations between different log entries. Summarize your findings in a structured format, highlighting the most critical issues and providing recommendations for addressing them.

Revert the specific change that caused the cascade issue in the codebase. Please identify the exact lines of code that were altered and explain the impact of these changes on the overall functionality. Additionally, provide a detailed analysis of why this change was problematic, including any potential side effects it may have introduced and suggestions for preventing similar issues in the future. Format your response as a report with clear sections for the change details, impact analysis, and recommendations.

Identify all dependencies that have been affected by the recent changes in the codebase. For each affected dependency, provide a detailed analysis of the impact of the change, including potential vulnerabilities or issues that may arise. Then, outline the necessary patches or updates required to resolve these issues, ensuring compatibility with existing code. Finally, summarize the steps taken to implement these patches and any testing that should be conducted to verify that the issues have been resolved.

Refactor the affected code in the [SPECIFIC_MODULE_OR_FUNCTION] to enhance its stability and prevent similar issues from arising in the future. Provide a detailed explanation of the refactoring approach you will take, including any design patterns or best practices applied. Additionally, outline the specific changes made, the expected impact on performance or reliability, and any potential risks or considerations that should be addressed during the refactoring process. Please present this information in a structured format, including code snippets where applicable.

Identify the specific line or section in the code that is causing the cascade issue. Provide a detailed explanation of the problem and implement a targeted fix that addresses this issue without impacting any other parts of the codebase. Include comments in the code to explain the changes made and why they are necessary. Additionally, outline any potential risks associated with the fix and how they can be mitigated. Format the response as a code snippet followed by the explanation.

Please review the current test suite for the project and identify any areas that lack sufficient test coverage, particularly in relation to the recent changes made. Update existing tests or create new ones to ensure that all affected areas are thoroughly tested. Each test should be designed to confirm that the fixes implemented are effective and that no new issues have been introduced. After updating or adding the tests, provide a summary of the changes made, including the specific areas covered and any tests that were added or modified.

Please run a comprehensive suite of tests to verify the resolution of the recent fix for [SPECIFIC ISSUE]. Include unit tests, integration tests, and any relevant system tests. Provide detailed results for each test, highlighting any errors or issues encountered, and confirm that there are no outstanding errors. Summarize the overall success of the testing process and any recommendations for further actions if necessary.

Please recreate the original scenario that led to the problem with [SPECIFIC ISSUE]. Describe the steps taken to reproduce the issue, including any relevant configurations or inputs used. Then, confirm whether the problem still occurs by detailing the current state after applying the resolution. Provide a clear comparison of the before and after states, highlighting any differences or improvements observed.

Please verify that all dependencies in the project are functioning correctly after the recent fix. List each dependency along with its current version and status, indicating whether it is stable or if there are any issues. Additionally, provide evidence of their stability, such as test results or logs from the latest build, and summarize any actions taken to resolve previous issues. Format the response in a clear, organized manner, highlighting any dependencies that may require further attention.

Please validate the integrity of the codebase after the recent fix. Check that all core functionalities are working as intended and ensure that no unrelated files or features have been negatively impacted. Provide a detailed report that includes any issues found, the files affected, and suggestions for resolving any problems. Additionally, confirm that all tests pass and summarize the overall health of the codebase in your findings.

Please re-examine the error logs after the recent fix has been applied. Confirm that all original errors have been resolved and that no new errors have been introduced in the system. Provide a summary of your findings, including the total number of errors identified before and after the fix, and any patterns or recurring issues that may still need attention. Additionally, suggest any further steps that may be necessary to ensure system stability and performance.

Draft a new rule for the CLAUDE.md document aimed at preventing recurrence of the recent issue related to breaking unrelated files. The rule should clearly outline the specific actions to be taken when encountering similar situations in the future. Include guidelines on how to identify potential problems, steps to mitigate risks, and any necessary protocols for documentation and communication. Format the rule as a concise statement that can be easily integrated into the existing CLAUDE.md structure.

Create a comprehensive pre-change checklist to follow before implementing changes that may impact multiple files. The checklist should include steps for verifying dependencies between files, ensuring compliance with relevant rules and standards, and assessing potential risks associated with the changes. Additionally, include a section for documenting the rationale behind each change and any necessary approvals required before proceeding. Format the checklist in a clear, organized manner with bullet points for easy reference.

Please add a comment above the fixed function warning in the code that clearly explains the specific constraint related to this function. The comment should be concise yet informative, summarizing the reason for the constraint and any relevant details that a developer should be aware of. Ensure that the comment is written in a way that is easy to understand and follows best practices for code documentation. The final comment should be formatted properly and ready to be integrated into the codebase.

Help me establish a system for setting up alerts that notify me of changes affecting critical dependencies in my project. Describe the specific criteria that should trigger these alerts, such as changes in version numbers, updates to related files, or modifications in configuration settings. Include details on how to configure the alerts, such as the preferred communication channels (email, messaging app, etc.), the frequency of notifications, and any thresholds that should be set to avoid alert fatigue. Additionally, explain how to ensure that the alerts are actionable and provide clear guidance on what steps to take when an alert is received.

Draft a session opener that emphasizes key considerations before starting work on similar tasks. The opener should include a brief overview of the importance of clarity in objectives, the need for effective communication among team members, and the significance of understanding potential challenges that may arise. Aim for a length of 3 to 5 sentences, ensuring it sets a positive and focused tone for the session. Include a call to action that encourages participants to share their thoughts or questions before diving into the work.