AI Prompts for Preventing Cascade Breaks in Files

Please provide a detailed list of all recent changes made to the project. For each change, indicate the specific files or features that were modified and highlight any changes that could potentially impact unrelated files or features. Additionally, explain the rationale behind each change and any expected effects on the overall project functionality. Format this information in a clear and organized manner, using bullet points for easy readability.

Please review the error logs generated during the last build. Identify any specific errors that could indicate a cascade break in unrelated files. For each error found, provide a brief explanation of its potential impact on the overall build process and suggest possible solutions or next steps to address these issues. Format your findings in a clear and organized manner, highlighting the most critical errors first.

Create a detailed dependency graph for the project named [PROJECT NAME]. Identify and highlight any dependencies that have been impacted by recent changes made in the last [TIME FRAME, E.G., "TWO WEEKS"]. Provide a brief analysis of how these changes may affect the overall functionality and stability of the project. Include any recommendations for addressing potential issues that arise from these dependencies. Format the output as a visual graph along with a written summary.

Please review the modified component and provide a comprehensive list of all components that interact with it. For each interaction, identify any unexpected behaviors or errors that may arise. Additionally, analyze the nature of these interactions and suggest potential solutions or adjustments to mitigate any issues. Format your response in a clear and organized manner, highlighting key findings and recommendations.

Please trace back the recent edits made to the specific lines of code in the project. Identify any changes that may have a cascading effect on unrelated files, and explain how these edits could potentially impact the overall functionality. Provide a summary of the findings in a structured format, highlighting the specific lines affected, the nature of the edits, and any recommendations for mitigating potential issues. Ensure the response is detailed and covers all relevant aspects of the codebase.

Please revert the most recent changes made to the project and analyze whether the cascade break still occurs after the reversion. Document the specific changes that were reverted and provide a detailed explanation of any remaining issues related to the cascade break. Additionally, suggest potential solutions or next steps to fully resolve the cascade break if it persists. Include any relevant observations or patterns you notice during this process.

Identify the specific line or block of code in my project that is causing the issue. Provide a detailed explanation of how this change impacts unrelated files, including the underlying reasons for the effect on those files. Additionally, suggest potential solutions or workarounds to mitigate the issue while maintaining the integrity of the overall codebase. Format your response clearly, outlining each step of your reasoning and any relevant examples.

Please analyze the identified problematic code in the application and apply a targeted fix. Ensure that the solution addresses the specific issue without impacting any other parts of the application. Provide a detailed explanation of the changes made, including the rationale behind the fix and any potential implications for future code maintenance. Additionally, include a brief test plan to verify that the fix works as intended and does not introduce new issues.

Please run isolated tests on the recent code changes made to address the issue with [SPECIFIC ISSUE]. Confirm that the fix effectively resolves the problem by providing a detailed report of the test results. Include information on any new problems that may have emerged during testing, and specify which tests were conducted, their outcomes, and any relevant metrics. Additionally, suggest any further actions or tests that may be necessary to ensure the stability of the code.

Please document the changes made to fix the issue of cascade breaks in the system. Include a detailed explanation of each change, focusing on how these modifications will prevent further cascade breaks in the future. Structure the documentation to include sections for the original issue, the specific changes implemented, and a rationale for how these changes address the underlying problems. Aim for a comprehensive overview that can serve as a reference for future maintenance and troubleshooting.

Re-run the scenario that previously caused the cascade break in the system. Please confirm whether the issue has been resolved and no longer occurs. Provide a detailed report on the results, including any observations or anomalies during the test. If the issue persists, outline the steps taken and any error messages encountered for further investigation.

Conduct regression testing on the entire project to verify that no new issues have been introduced. Please outline the specific areas of the project that need to be tested, including any recent changes or updates. Provide a detailed report of the testing results, highlighting any issues found, their severity, and recommendations for resolution. Additionally, include a summary of the overall stability of the project after testing, and any areas that may require further attention. Format the report in a clear and organized manner for easy review.

Please review the outputs from the tests that were run after the recent fix. Confirm that all tests have passed successfully and provide a summary of the results. If any tests failed, please detail which ones did not pass and suggest potential reasons for the failures. Additionally, include any observations or insights about the overall performance of the system after the fix.

Please validate that all component interactions are functioning correctly after the recent fix. Test each interaction thoroughly and document any anomalies or issues that arise during the validation process. Include details such as the specific components tested, the nature of any issues found, and any steps taken to reproduce the anomalies. Provide a summary of the overall functionality and any recommendations for further action if necessary.

Please verify the stability of all dependencies after the recent changes. List each dependency and indicate whether it remains stable or if any new errors have emerged. Additionally, provide a brief explanation for any dependencies that are affected, including the nature of the changes and potential impacts on the overall system. Format your findings in a clear report that highlights any issues and suggests next steps for resolution.

Draft a new rule for CLAUDE.md aimed at preventing cascade breaks similar to the recent issue encountered. The rule should clearly outline the conditions that trigger a cascade break and specify the actions to be taken to mitigate these risks. Include guidelines on how to identify potential unrelated files that could contribute to the issue and suggest best practices for maintaining file integrity. Format the rule in a clear and concise manner, ensuring it can be easily understood and implemented by team members.

Please provide a detailed comment to be placed above the fixed code that clearly explains the specific constraint that must not be violated. The comment should include the nature of the constraint, why it is important, and any potential consequences of violating it. Ensure the comment is concise yet informative, ideally no longer than three sentences. Format the comment as a single line of code that can be easily integrated into the existing codebase.

Create a comprehensive pre-edit checklist to ensure all necessary steps are taken before making any edits to a document. The checklist should include items such as verifying the integrity of the original files, checking for dependencies that could lead to cascade breaks, confirming that all related documents are updated, and ensuring that all stakeholders have reviewed the changes. Additionally, include steps for backing up the original files and a review process to catch any potential issues before edits are finalized. Format the checklist in a clear, organized manner for easy reference.

Draft comprehensive guidelines for ensuring component isolation in software development to prevent unintended interactions between components. Include specific practices such as using clear interfaces, maintaining separate state management for each component, and implementing strict access controls. Additionally, outline the importance of thorough testing and validation processes to identify potential issues early. Format the guidelines in a numbered list for clarity, and provide examples where applicable to illustrate each point effectively.

Please help me create a comprehensive rule for monitoring dependencies in a project after each change is made. Outline the specific steps involved in the monitoring process, including how to identify dependencies, the tools or methods to use for tracking changes, and the frequency of monitoring checks. Additionally, explain how to document any issues that arise and the procedures for addressing them. Ensure that the rule is clear and actionable, allowing for easy implementation by the team.