AI Prompts for Fixing Cascade Breaks in Cursor

Please provide a detailed list of all recent changes made across the project. For each change, indicate whether it has the potential to impact unrelated files and explain how. Additionally, summarize the overall implications of these changes on the project as a whole. Aim for clarity and structure in your response, ensuring that each change is clearly outlined with relevant details.

Analyze the dependencies of the modified files in the project. Identify any dependencies that may have caused issues in unrelated files and explain the nature of these links. Provide a detailed report that includes the names of the modified files, the specific dependencies involved, and a clear explanation of how these dependencies interact with other files in the system. Additionally, suggest potential solutions or workarounds for any identified issues.

Examine the error logs generated after the last edit and identify any errors that indicate issues in unrelated files. For each error found, provide a detailed explanation that includes the error message, the potential cause of the issue, and any relevant context that may help in understanding the impact of these errors. Additionally, suggest possible solutions or next steps to address each identified error. Format your response in a clear and organized manner, using bullet points or numbered lists for clarity.

Trace the function calls from the modified files in the codebase. Identify any function calls that could potentially affect unrelated files and explain how these calls might impact the overall functionality and stability of the application. Provide specific examples of the affected files and describe the nature of the impact, including any risks or issues that may arise as a result of these function calls. Format your response in a clear, structured manner, highlighting key points for easy reference.

Please analyze the project tree for [PROJECT NAME] to understand its structure and the relationships between the files. Identify any structural changes that may have contributed to the current issues we are facing. Provide detailed insights into these changes, including specific files or folders that were altered, the nature of the changes, and how they might affect the overall functionality of the project. Additionally, suggest potential solutions or adjustments that could help resolve the issues identified.

Please help me identify the specific change that is causing the current issue in the project. Once identified, provide a detailed explanation of why this change is problematic and how it impacts the overall functionality. After that, guide me through the process of reverting this change while ensuring that no other modifications are affected. Include any potential risks or considerations I should be aware of during this process.

Please modify the dependency handling in the affected files while ensuring that these changes do not impact any unrelated files. Clearly outline the specific adjustments made to the dependency management process, including any code snippets or configuration changes necessary. Additionally, provide a detailed explanation of the rationale behind each adjustment and how it improves the overall functionality or stability of the project. Format your response in a structured manner, with headings for each section and bullet points for clarity.

Identify and analyze the functions that were recently modified in the codebase. Look for any logical errors or inconsistencies in their implementation. For each identified error, provide a detailed correction along with an explanation of the logic behind the changes made. Additionally, ensure that any modifications do not impact unrelated files or functions within the project. Present your findings in a structured report format that includes the original code, the corrected code, and the rationale for each correction.

Please review the current configuration settings for [SPECIFIC SYSTEM OR APPLICATION] to identify any that may be causing issues. Update these settings as necessary, ensuring that the changes do not impact any unrelated files or systems. After making the updates, provide a detailed summary of the changes made, including the original settings and the reasons for the adjustments. Additionally, include any potential implications of these changes on the overall system performance.

Refactor the code in the affected files to enhance stability while ensuring that unrelated files remain unaffected. Provide a detailed explanation of the refactoring process, including the specific changes made to improve stability, any design patterns or best practices applied, and how these changes contribute to overall code quality. Additionally, outline any potential risks associated with the refactoring and how they can be mitigated. Format the explanation in a clear, step-by-step manner to facilitate understanding.

Please run a comprehensive suite of tests to verify the effectiveness of the recent fix for [SPECIFIC ISSUE]. Include both automated and manual tests as appropriate, and provide detailed results for each test conducted. Additionally, confirm that any unrelated files or components within the system remain unaffected by this fix. Summarize your findings in a report format, highlighting any issues encountered and the overall impact on system functionality.

Please recreate the original scenario that caused the issue related to breaking unrelated files. Detail the steps taken to reproduce the scenario, including any specific conditions or configurations that were present. After reproducing the issue, confirm whether the problem still occurs and provide a clear before and after comparison of the results. Include any relevant metrics or observations that highlight the differences between the two states.

Please verify the integrity of all files after the recent fix has been applied. Ensure that no unrelated files have been impacted during this process. Provide a detailed summary of the integrity check, including any discrepancies found, the total number of files checked, and a clear statement on whether the integrity of the files is intact. If any issues are identified, please outline the specific files affected and recommend next steps for resolution.

Please validate the dependency links within the project. Check that all dependencies are correctly linked and functioning as intended. Additionally, confirm that any recent changes made do not adversely affect unrelated files. After your assessment, provide a detailed report that includes any discrepancies found, the status of each dependency, and recommendations for resolving any issues identified.

Please test the functionality of the modified files to ensure they perform as expected. Specifically, verify that these changes do not impact any unrelated files. Document the outcomes of your tests, including any issues encountered, and provide a summary of the overall functionality. If any discrepancies arise, detail the specific files affected and the nature of the issues.

Please create a new rule for managing dependencies in the CLAUDE.md file that effectively prevents cascade issues. The rule should clearly outline the conditions under which dependencies can be added or modified, and specify any limitations to avoid conflicts. Include examples of scenarios that would trigger this rule and how to handle them. Provide the exact text that can be directly added to the CLAUDE.md file for implementation.

Please provide a set of comments to insert above critical functions in my codebase. These comments should warn about potential impacts on unrelated files and specify the nature of those impacts. Include examples of how to phrase these comments effectively, ensuring they are clear and concise. Additionally, suggest best practices for maintaining these comments as the code evolves to prevent confusion in the future.

Please develop a comprehensive change checklist that can be used before implementing any modifications to a system or project. The checklist should include specific steps to prevent cascade issues, such as reviewing dependencies, assessing potential impacts, and ensuring proper communication with all stakeholders. Additionally, include sections for documenting the change rationale, testing procedures, and post-implementation review. Format the checklist in a clear, organized manner with bullet points for easy reference.

Please create a comprehensive set of session guidelines to be followed at the start of each session. These guidelines should focus on preventing recurrence of issues related to breaking unrelated files. Include specific steps to ensure clarity and organization, such as defining roles, setting expectations for communication, and outlining procedures for addressing potential conflicts. The guidelines should be structured in a clear format, with each point numbered and explained in detail to facilitate easy understanding and implementation.

Help me define clear conventions for making changes across the project to prevent cascade issues. The conventions should cover guidelines for naming conventions, file organization, and documentation practices. Include specific examples of how to implement these conventions effectively and outline the potential pitfalls to avoid. Format the conventions in a structured document with headings for each section, and ensure it is comprehensive enough for team members to follow easily.