AI Prompts for Preventing Cascade Breaks in Replit

Please provide a detailed report of all changes made during the last session. Include a comprehensive list of every file that was modified, along with the specific line numbers that were affected. Additionally, highlight any changes that could potentially impact unrelated files, explaining how these changes might create dependencies or issues. Format the report in a clear, organized manner for easy reference.

Please help me trace the source of the following error message: [PASTE ERROR MESSAGE]. Analyze the context in which this error occurred and identify the most recent changes made in the codebase that could have led to this issue. Provide a detailed explanation of the root cause, including any relevant code snippets or logic that may be contributing to the error. Additionally, suggest potential solutions or fixes to resolve this error effectively.

Analyze the dependencies in my project to determine their current status and any potential issues. Identify any recent changes made to these dependencies, including updates or removals, that could have impacted their functionality. Additionally, provide a summary of how these changes might have contributed to the current issue I am facing. Please format your findings in a clear report, highlighting the most critical dependencies and any recommended actions to resolve the issues.

Please review the current environment variables set in the system. Provide a comprehensive list of these variables, including their values and any relevant descriptions. Additionally, analyze any recent changes made to the environment that could have impacted these variables and contributed to the current issue. Summarize your findings in a structured format, highlighting any discrepancies or potential causes for concern.

Please analyze the recent changes made to the codebase and examine how they interact with the existing code. Identify any unexpected interactions or conflicts that may have led to unrelated features breaking. Provide a detailed report that includes specific lines of code affected, the nature of the interactions, and any potential solutions or recommendations to resolve these issues. Additionally, summarize the overall impact of these changes on the functionality of the application.

Revert the last change made to [SPECIFIC FILE OR FEATURE] and provide a detailed explanation of why this change may have caused the issue. Include specific examples of how the change could impact the functionality or performance of the project. Additionally, suggest an alternative approach that could achieve the desired outcome without introducing the same problems. Please format your response in a clear, structured manner, outlining the steps taken and the rationale behind the alternative solution.

Identify any incorrect dependency changes in the project. For each error found, provide a detailed explanation of how it impacts unrelated files within the codebase. Additionally, suggest specific corrections to resolve these dependency issues and describe the potential consequences of not addressing them. Format your response in a clear, structured manner, including examples where applicable.

Identify any environment variable issues in my project related to [SPECIFIC ISSUE] and provide a detailed explanation of how to adjust them correctly. For each variable, specify the current incorrect value and the correct value it should be set to. Additionally, explain how these changes will resolve the underlying issues and improve the functionality of the project. Include any potential impacts these adjustments may have on other parts of the system.

Please analyze the codebase for [PROJECT NAME] to identify specific interactions between files that are causing issues. Once you have pinpointed the problematic interactions, modify the relevant sections of the code to prevent these issues from occurring in the future. Provide a detailed explanation of the changes you made, including the rationale behind each modification and how it resolves the interaction problems. Additionally, suggest any best practices to avoid similar issues in the future.

Please restore the project to the last known working state. Identify the specific changes that led to the current issue and provide a detailed analysis of each change. Additionally, suggest a step-by-step plan to safely reintroduce these changes, including any necessary testing or validation steps to ensure stability. Format your response as a clear report with sections for the identified changes, the proposed reintroduction plan, and any potential risks involved.

Please run a comprehensive suite of tests to verify that the issue with [SPECIFIC ISSUE] is fully resolved. Include details on each test conducted, the results obtained, and any discrepancies or remaining issues that may still exist. Additionally, provide a summary of the overall testing process, highlighting any areas that may require further investigation or attention. Format the results in a clear and organized manner, ensuring that each test outcome is easy to understand.

Please recreate the original scenario that caused the problem with [SPECIFIC DETAILS ABOUT THE SCENARIO]. Once you have reproduced it, confirm whether the issue still occurs. If the problem has been resolved, provide evidence of the resolution, such as screenshots, error messages, or a detailed description of the steps taken to verify that the issue is no longer present.

Please verify the functionality of unrelated features after the recent fix. Provide a detailed list of each feature that is supposed to be functioning correctly, along with any that are still exhibiting issues. For each feature, include a brief description of its intended function, the specific issues encountered, and any error messages or unexpected behaviors observed. Additionally, indicate whether the issue is critical, minor, or requires further investigation.

Please verify the stability of all dependencies in the project. List each dependency along with its current version and indicate whether it is functioning as expected. If there are any issues related to dependencies, provide a detailed summary of each issue, including the nature of the problem, potential impacts on the project, and any recommended steps for resolution. Format your response as a clear report that I can use to address any outstanding concerns.

Please validate the environment variables for my project. List all the environment variables currently set and check that each one is functioning correctly. If any issues are detected, provide a detailed explanation of the problem and suggest possible solutions. Additionally, confirm that these variables do not cause any conflicts or errors in the application. Format your response in a clear, structured manner.

Draft a comprehensive rule for managing dependencies in CLAUDE.md that outlines best practices to prevent issues in future sessions. The rule should cover key aspects such as version control, documentation of dependencies, regular updates, and the importance of testing after changes. Include specific examples of common pitfalls to avoid and a checklist for maintaining dependency integrity. Format the rule as a clear guideline that can be easily referenced by team members.

Please generate a comment to be inserted in the codebase that warns developers about specific interactions that must be avoided. The comment should clearly state the potential issues that can arise from these interactions and provide guidance on how to prevent them. Make sure the comment is concise yet informative, ideally no more than three sentences long, and formatted in a way that is easy to read and understand. Include examples of the interactions to avoid and any relevant context that would help a developer understand the importance of this warning.

Create a comprehensive checklist for setting environment variables correctly. The checklist should include steps such as identifying the required variables, ensuring proper naming conventions, verifying values for accuracy, and testing the environment after changes. Additionally, include reminders about documenting changes and reviewing security implications. Format the checklist in bullet points for easy reference, and ensure it can be used at the start of any session involving environment changes.

Help me establish a comprehensive change review protocol for our project. The protocol should outline the steps for reviewing changes before implementation, including criteria for approval, roles and responsibilities of team members involved in the review process, and a timeline for review completion. Additionally, provide guidelines for documenting feedback and decisions made during the review process. Finally, format this protocol in a clear and organized manner suitable for inclusion in a document titled CLAUDE.md.

Create a feature impact assessment checklist that evaluates the potential impacts of changes on unrelated features within a project. The checklist should include sections for identifying the feature being changed, potential risks to unrelated features, dependencies that may be affected, and mitigation strategies to address those risks. Additionally, include a section for assessing the overall impact on user experience and system performance. Format the checklist in a clear and organized manner, making it easy to use in future evaluations.