AI Prompts for Preventing Module Export Breaks

Please identify all the exports in the module located at [MODULE FILE PATH] that have been modified. For each export, provide a detailed description of what specific changes were made, including the original and modified versions. Additionally, explain the reasoning behind each change and how it impacts the overall functionality of the module. Format your response in a clear, structured manner, using bullet points for each export to enhance readability.

Please analyze the import dependencies for the module located at [MODULE FILE PATH]. List all files that import from this module and provide details on their import statements. Highlight any discrepancies between the imports in these files and the current exports from the module, including missing or incorrectly referenced imports. Present the findings in a clear format, indicating which files have issues and the specific discrepancies found.

Please review the actions taken in Cascade mode for the module located at [MODULE FILE PATH]. Provide a detailed explanation of each action, including any modifications made to related files. Specifically, indicate whether any imports were updated or left unchanged, and discuss the potential implications of these changes on the overall functionality of the module. Additionally, summarize any best practices that should be followed when making such modifications to ensure consistency and maintainability.

Please analyze the export consistency of the module located at [MODULE FILE PATH]. Compare the current exports with those from the previous version, and identify any inconsistencies or discrepancies you observe. Provide a detailed report that includes specific examples of the inconsistencies, their potential impact on the overall functionality, and any recommendations for addressing these issues. Format your findings in a clear, structured manner, highlighting key differences and suggesting possible solutions.

Please provide a detailed list of any unintended changes made to the module located at [MODULE FILE PATH] during the last edit session. Include specific information about the type of changes, such as modifications to code, alterations in dependencies, or any adjustments to configurations. For each change, indicate the line number where the change occurred and a brief description of what the original state was versus the new state. Format this list clearly, so it can be easily reviewed for further analysis.

Please review each file that imports from [MODULE FILE PATH] and update the import statements to ensure they accurately reflect the current exports. Provide a detailed list of changes made, including the original import statements and the updated versions. Additionally, check for any deprecated imports that may need to be removed and note any files that require further attention due to potential issues with the imports. Ensure that the updated import statements follow best practices for clarity and maintainability.

Identify and revert any changes made to [MODULE FILE PATH] that are unnecessary for the intended fix. Provide a detailed summary of the changes that were reverted, explaining why each was deemed unnecessary. Ensure that the final version of the module is clean and only includes the essential modifications needed for the fix. Additionally, list any potential impacts these changes may have on the overall functionality of the module.

Please review the export changes made in [MODULE FILE PATH] and ensure that these updates are accurately reflected in all relevant importing files. Identify any discrepancies or areas where the changes have not been applied. After completing the synchronization, provide a detailed summary of the updates made, including which files were affected and any issues encountered during the process. Format the summary in a clear, organized manner for easy reference.

Please validate the integrity of the exports located in [MODULE FILE PATH]. Confirm that these exports meet the specified project requirements, including data format, completeness, and accuracy. Provide a detailed report outlining any discrepancies found, along with suggestions for corrections. Additionally, include a summary of how the exports can be improved to better align with the project goals.

Please review the edits made in Cascade mode for the file located at [MODULE FILE PATH]. Identify any corrections needed to ensure that the functionality and integrity of the module are preserved. Provide a detailed list of the specific edits that require correction, explaining why each edit is incorrect and suggesting the appropriate changes. Additionally, summarize the overall impact of these corrections on the module's performance and functionality.

Please verify that all import statements across the project are consistent with the current exports of [MODULE FILE PATH]. Provide a detailed report highlighting any inconsistencies found, including the specific files and lines where the discrepancies occur. Additionally, suggest corrections for any identified issues to ensure that all imports align properly with the exports. Format the report in a clear and organized manner, making it easy to follow and implement the necessary changes.

Please execute comprehensive tests for all functionalities that depend on [MODULE FILE PATH]. Ensure that each function is tested under various scenarios to confirm they are working as expected. Provide a detailed report of the test results, including any errors encountered, the expected outcomes, and the actual outcomes for each functionality. Additionally, summarize any areas that may require further attention or improvement based on the test findings.

Please verify that all exports in [MODULE FILE PATH] are correctly synchronized with their corresponding imports. List any discrepancies you find, including details on which exports are not aligned with their imports and the reasons for any issues. Additionally, provide recommendations on how to resolve these discrepancies to ensure full synchronization. Format your response in a clear and organized manner, highlighting key findings and suggested actions.

Generate a comprehensive import-export report for the data located at [MODULE FILE PATH]. The report should include an overview of the current state of imports and exports, detailing any issues that have been resolved in the last quarter. Additionally, provide insights into trends observed in the data, any outstanding concerns that may need attention, and recommendations for optimizing the import-export process moving forward. Format the report with clear headings and bullet points for easy readability, and ensure it is at least two pages long.

Please assess the overall stability of the project following the recent export-import alignment. Identify and report any remaining issues that could affect the project's performance or reliability. Include specific details about the areas that require attention, potential risks, and suggestions for improvement. Format your findings in a clear report with sections for each identified issue, including a brief description, impact assessment, and recommended actions.

Please draft a new export rule for CLAUDE.md that ensures any exports in [MODULE FILE PATH] cannot be modified unless there are corresponding updates to the imports. The rule should clearly outline the conditions under which modifications can occur, specify the process for updating imports when changes are made to exports, and include any necessary checks or balances to enforce compliance. Additionally, provide examples of scenarios where this rule would apply and potential consequences for failing to adhere to it. Format the rule in a clear and structured manner suitable for inclusion in the documentation.

Create a detailed checklist item for session openers that ensures import consistency verification whenever there are changes to module exports. The checklist should include steps to identify affected modules, guidelines for testing the imports after changes, and a reminder to document any discrepancies found during the verification process. Additionally, outline the importance of maintaining import consistency for project stability and provide examples of common issues that may arise from inconsistencies. Format this as a clear, actionable item that can be easily referenced during development sessions.

Create a detailed template for documenting export changes in the module located at [MODULE FILE PATH]. The template should include sections for the date of the change, a description of the change made, the reason for the change, the name of the person who made the change, and any relevant notes or impacts on existing functionality. Ensure that the format is clear and easy to follow, allowing for consistent updates and a comprehensive change history. Additionally, provide an example entry to illustrate how to fill out the template effectively.

Propose a detailed naming convention for exports in the module located at [MODULE FILE PATH]. The convention should aim to minimize the risk of import mismatches and enhance code readability. Include guidelines on how to structure the names, such as using prefixes or suffixes that indicate the type of export, and suggest any specific formats or patterns that should be followed. Additionally, provide examples of both good and bad naming practices to illustrate the impact of following or ignoring this convention.

Create a comprehensive set of guidelines for utilizing Cascade mode effectively to prevent unintended changes to module exports and imports. The guidelines should include: a detailed explanation of what Cascade mode is and how it functions, specific scenarios where it is beneficial, and best practices for implementation. Additionally, provide examples of common pitfalls to avoid when using Cascade mode, and outline the steps to troubleshoot issues that may arise. Format the guidelines as a clear, structured document with sections and bullet points for easy reference.