AI Prompts for Correcting Package Version Mismatches

Please check the installed version of [PACKAGE_NAME] in my project. Provide the exact version number along with any relevant information about the installation date and any potential compatibility issues with other packages. Additionally, if there are any updates available for this package, please list those as well.

Please check the installed version of [PACKAGE_NAME] and determine if it is compatible with the other dependencies in my project. Provide a detailed analysis of any conflicts that may arise, including the specific versions of the conflicting dependencies and suggestions for resolving these issues. Additionally, summarize the potential impact of these conflicts on my project's functionality and performance. Format your response in a clear, organized manner for easy reference.

Please provide the dependency tree for [PACKAGE_NAME]. I want you to identify and highlight any outdated or incompatible versions within the tree. Additionally, include a brief explanation of the potential impact of these issues on the overall functionality of the package. Format the output in a clear and organized manner, making it easy to understand the relationships and version statuses.

Please analyze the contents of my CLAUDE.md file, which I will provide below: [PASTE CONTENT]. Identify any package version rules that have not been followed according to standard compliance guidelines. For each rule that is violated, please provide a brief explanation of the issue, including the specific version numbers involved and suggestions for how to correct them. Format your response in a clear, organized manner, listing each violation with its corresponding details.

Please examine the recent changes made to the package.json or requirements file for the project. Identify any modifications that may have led to the current version issue. Provide a detailed summary of the changes, including the specific lines that were altered, added, or removed, and explain how each change could potentially impact the package version. Additionally, suggest steps to resolve the version conflict based on your analysis.

Please update the package [PACKAGE_NAME] to the latest compatible version based on the guidelines outlined in my CLAUDE.md file. Ensure that the update adheres to all specified compatibility rules and does not introduce any breaking changes. Provide a summary of the changes made, including the previous version and the new version, along with any relevant notes on compatibility or potential issues to watch for after the update.

Revert [PACKAGE_NAME] to the last known working version. Please check the version history and confirm the specific version number that was previously functioning correctly. Once confirmed, provide the necessary steps to uninstall the current version and install the specified previous version, ensuring that all dependencies are also addressed. Include any potential issues that may arise during this process and how to resolve them.

Please modify the dependency rules in the CLAUDE.md file to enforce the correct version of [PACKAGE_NAME]. Clearly outline the changes you made, including any specific version constraints or requirements that should be applied. Additionally, provide a brief explanation of why these changes are necessary for ensuring compatibility and stability in the project. Format your response in a way that highlights the original rules and the modified rules for easy comparison.

Please identify any packages that are conflicting with the required version of [PACKAGE_NAME] in my environment. Once identified, provide detailed instructions on how to remove these conflicting packages, including the specific commands to execute. After removing the packages, list all changes made to ensure clarity on what was altered in the environment. Additionally, suggest any steps to verify that the required version of [PACKAGE_NAME] is now properly installed and functioning.

Create a lock file that specifies the exact versions of [PACKAGE_NAME] and all its dependencies to ensure compatibility. Include a detailed list of each package along with its version number, and explain how this lock file will prevent issues during installation or updates. Additionally, provide instructions on how to generate this lock file in the appropriate format for the package manager being used. Make sure to highlight any potential conflicts that could arise if versions are not locked properly.

Please perform a dependency check to confirm that all packages are compatible after the recent installation. Provide a detailed report that includes the names and versions of each package, any conflicts detected, and suggestions for resolving those conflicts if applicable. Additionally, indicate whether any packages need to be updated or replaced to ensure compatibility. Format the results in a clear and organized manner for easy review.

Please build the project and verify that the build completes successfully without any errors related to [PACKAGE_NAME]. After the build, provide a detailed report on any issues encountered during the process, including error messages and their potential causes. Additionally, confirm that all necessary dependencies are correctly installed and functioning as expected. If any errors are found, suggest possible solutions or steps to resolve them.

Please run all unit tests for the project to verify that no functionality has been broken as a result of the recent package version change. Provide a summary of the test results, including any failures and their corresponding error messages. Additionally, outline any areas of the code that may require further investigation based on the test outcomes. Ensure that the report is clear and structured, making it easy to identify issues that need to be addressed.

Please review the current setup and verify its compliance with all the rules outlined in the CLAUDE.md file. Provide a detailed assessment of any areas where the setup meets the requirements and highlight any discrepancies or non-compliance issues. Additionally, suggest corrective actions for any identified non-compliance to ensure full adherence to the guidelines. Format your response in a clear and organized manner, summarizing the findings and recommendations.

Please generate a comprehensive compatibility report for the project dependencies. Include the following sections: a list of all current dependencies with their versions, a summary of compatibility issues identified, recommendations for resolving any conflicts, and a comparison of the current versions against the latest stable releases. Additionally, provide insights on potential impacts of upgrading or downgrading specific dependencies on the overall project functionality. Format the report as a structured document with headings and bullet points for clarity.

Please draft a new version rule for the CLAUDE.md documentation to prevent future package version mismatches. The rule should clearly outline the steps developers must follow when specifying package versions, including guidelines on version ranges, compatibility checks, and how to handle deprecated packages. Additionally, include examples of correct and incorrect version specifications to illustrate the rule effectively. Ensure the text is concise, clear, and suitable for inclusion in the documentation.

Please add a detailed comment in the package.json or requirements file that explains the version constraints for [PACKAGE_NAME]. The comment should clarify why specific versions are required, including any compatibility issues or features that are only available in those versions. Additionally, provide context on how these constraints impact the overall project and any potential risks of using different versions. Ensure the comment is clear and informative for future developers who may work on this project.

Create a comprehensive checklist for initiating new sessions in a development environment. The checklist should include steps such as verifying package versions against the CLAUDE.md file, ensuring all necessary dependencies are installed, confirming the correct configuration settings are applied, and reviewing any recent updates or changes in the project documentation. Additionally, include a section for noting any issues encountered in previous sessions and steps taken to resolve them. Format the checklist in a clear, organized manner that allows for easy tracking and completion.

Please suggest a detailed naming convention for version tags that clearly indicates compatibility with the project’s dependencies. The convention should include specific elements such as major, minor, and patch version numbers, as well as any relevant identifiers for dependencies or compatibility levels. Additionally, provide examples of how this naming convention would be applied in practice, and explain how it can help prevent issues related to version mismatches in the future. Aim for a format that is easy to understand and implement across the project.

Help me create a project guard script that automatically checks for version mismatches in dependencies before allowing commits to the repository. The script should validate the versions specified in the [PACKAGE_FILE] against the installed versions in the environment. If a mismatch is detected, it should prevent the commit and provide a clear error message indicating the discrepancies. Additionally, include instructions on how to set up and run this script within a [PROGRAMMING_LANGUAGE] project. Ensure the solution is robust and can be easily integrated into existing workflows.