AI Prompts for Addressing Nonexistent Imports

Please analyze the current file and list all the imports present in it. Next, cross-reference these imports with the project structure to identify any imports that are missing or do not exist. Provide a detailed list of these nonexistent imports, including any relevant information about where they were expected to be found in the project structure. Format the output in a clear and organized manner for easy reference.

Please analyze the following error messages: [PASTE ERROR MESSAGES]. Identify which specific imports are leading to these errors and provide a detailed explanation of why these imports might be missing. Additionally, suggest potential solutions or steps I can take to resolve these issues. Format your response in a clear and organized manner, including any relevant code snippets or examples that could help clarify the solutions.

Please review the project tree and confirm the existence of modules or files for the following imports: [LIST OF IMPORTS]. For each import, indicate whether the corresponding file exists or not. If any imports do not have corresponding files, list them clearly along with a brief explanation of what each import is intended for. Additionally, provide suggestions on how to resolve any missing imports to ensure the project functions correctly.

Please review the recent changes made to the files that include the following imports: [IMPORTS LIST]. Identify and highlight any modifications that may have introduced nonexistent imports. Provide a detailed summary of the changes, including the specific lines of code affected and an explanation of how these changes could lead to the issue. Additionally, suggest possible solutions or corrections to address the problem.

Please review the configuration settings related to import resolution in my project. Identify any rules or paths that may be affecting how imports are being resolved. If you find any discrepancies or issues that could lead to missing imports, please provide a detailed report outlining these problems and suggest possible solutions to rectify them. Include any relevant examples or scenarios where these discrepancies might occur to help clarify the issues.

Please review the following code and remove any nonexistent imports listed here: [LIST IMPORTS]. After removing these imports, ensure that the rest of the code does not depend on them, and provide a brief summary of any changes made. Additionally, check for any potential issues that may arise from these removals and suggest any necessary adjustments to maintain the code's functionality. Format your response to clearly indicate the original imports removed and the final version of the code.

Please create placeholder modules for the following imports: [LIST IMPORTS]. Each module should have the expected structure and interfaces that align with typical usage in a project. Include at least one function or class in each module that demonstrates how it would be used in practice. Additionally, provide comments within the code to explain the purpose of each module and any important details that a developer should know when implementing them.

Please review the import paths in my project and identify any that are incorrect due to path issues. Based on the project structure, provide a corrected list of these import paths. For each change made, include the original path, the corrected path, and a brief explanation of why the correction was necessary. Ensure the final output is clear and organized for easy reference.

Refactor the following code to utilize existing modules instead of nonexistent ones. The code is as follows: [INSERT CODE HERE]. After making the necessary changes, provide a detailed list of the modifications made, including the specific modules that were replaced and the rationale behind each change. Additionally, explain how these adjustments improve the overall functionality and maintainability of the code. Aim for a clear and organized format that highlights the before-and-after states of the code.

Please review the current configuration rules for the project and identify any discrepancies with the existing project structure that could lead to import errors. Provide a detailed list of the updated rules, including specific changes made and the rationale behind each update. Ensure that the new rules are clearly defined and easy to understand, and format the output as a structured document with headings for each rule. Additionally, include any best practices that should be followed to prevent future import issues.

Please run tests that specifically target the imports that were recently fixed in the codebase. Provide a detailed report of the test results, including any errors or warnings encountered during the testing process. Confirm that there are no remaining import errors and summarize the overall success of the tests. Include any relevant information about the environment in which the tests were run and any steps taken to resolve previous issues.

Please review the project structure for [PROJECT NAME] to ensure that all necessary modules are present and correctly referenced. Identify any missing modules or incorrect references and provide a detailed list of these issues. Additionally, suggest any steps that can be taken to resolve these problems and ensure the project is fully functional. Format your response in a clear, organized manner, highlighting the key areas that need attention.

Please validate the configuration changes that have been made to the system. Confirm whether these changes have been applied correctly and assess their effectiveness. Include a detailed analysis of the impact of these changes on system performance and functionality. If there are any discrepancies or issues, please highlight them and suggest possible solutions.

Please review the codebase for consistency in import usage across all files. Identify any discrepancies in how imports are structured and used, noting specific files and lines where inconsistencies occur. For each discrepancy, provide a suggested resolution or correction to ensure uniformity in import statements. Additionally, summarize the overall findings in a report format, highlighting key areas that require attention and any patterns observed in the inconsistencies.

Reproduce the scenario that previously caused import errors in the system. Provide a detailed account of the steps taken to recreate the issue, including any specific configurations or settings used. After demonstrating the error, confirm that it no longer occurs by showing the current state of the system and any changes made to resolve the issue. Include a comparison of the before and after states, highlighting the differences and improvements achieved.

Please create a comprehensive checklist for verifying imports in a codebase before committing changes. The checklist should include steps to confirm that all imports are present in the project, properly referenced in the code, and adhere to the project's coding standards. Additionally, include checks for unused imports and any necessary documentation updates related to the imports. Format the checklist in a clear, bulleted list for easy reference, and ensure it covers both common scenarios and edge cases.

Please draft a new rule for the CLAUDE.md document aimed at preventing import issues that have recently occurred. The rule should clearly outline the specific guidelines and practices to follow to avoid these problems in the future. Include examples of what constitutes acceptable and unacceptable imports, and specify any necessary checks or validations that should be implemented. Format the rule in a clear and concise manner, suitable for inclusion in the existing document.

Please generate a comment that should be placed above the import section in each file. The comment should clearly outline the specific constraints and checks that need to be considered for imports, including any potential issues that may arise if these constraints are not followed. Make sure the comment is concise yet informative, ideally no longer than five sentences, and uses clear language that can be easily understood by developers. Format the comment as a code snippet that can be directly copied and pasted into the files.

Create a detailed session opener checklist for a coding session that ensures all necessary imports are verified. The checklist should include specific steps to prevent missing imports, such as reviewing the project requirements, listing all required libraries, and checking for any recent changes in dependencies. Additionally, include a step for confirming that all imports are correctly referenced in the code. Format the checklist in a clear, actionable way, with each step numbered for easy reference.

Create a comprehensive naming convention guide for modules and files that will ensure consistent import paths across the project. The guide should include specific rules for naming modules, such as using lowercase letters, avoiding special characters, and using underscores for readability. Additionally, outline best practices for organizing files within directories to maintain clarity and ease of navigation. Include examples of good and bad naming practices, and suggest a standardized format for naming that can be easily followed by all team members. Format the guide as a structured document with headings and bullet points for clarity.