AI Prompts for Identifying Unnecessary Dependencies

Please provide a detailed list of the current dependencies installed for this project. Include the name and version of each dependency, and specifically highlight any that were added during the last session. Additionally, for each new dependency, provide a brief description of its purpose and how it contributes to the overall functionality of the project. Format the response in a clear and organized manner, such as a table or bullet points, to enhance readability.

Analyze the current codebase of my application and identify which installed packages are not being utilized in any part of the code. Provide a detailed list of these unused packages, including their names and versions. Additionally, explain the potential impact of removing these packages on the application’s performance and functionality. Format the response in a clear table with columns for package name, version, and notes on any dependencies that may be affected.

Please provide a detailed list of all changes made during the last session. Focus specifically on any new dependencies that were added, including their names, versions, and the reasons for their inclusion. Additionally, summarize how these changes might impact the overall project and any potential issues that could arise from these new dependencies. Format the response as a structured report with clear headings for each section.

For each dependency that has been added recently, provide a detailed explanation of its purpose and how it specifically supports the requested feature. Include information on the functionality it provides, any potential impact on performance or security, and how it integrates with existing components. Additionally, assess whether this dependency is essential for the feature or if there are alternative solutions that could be considered. Format your response in a clear and organized manner, with each dependency listed separately.

Please compare the installed dependencies of the project with the requirements for the requested feature, [FEATURE NAME]. Identify and highlight any dependencies that do not directly support the functionality of this feature. For each unnecessary dependency, provide a brief explanation of why it is not needed and suggest alternatives if applicable. Format the output as a detailed report that includes the names of the dependencies, their current roles, and recommendations for streamlining the project.

Please analyze the codebase for any unused dependencies and provide a detailed list of those that can be safely uninstalled. For each dependency identified, explain why it is considered unused and confirm that it is not required for any part of the code. Once I review the list, I would like to proceed with the uninstallation of each dependency, ensuring that I have the option to confirm each removal before it is executed. Format the output in a clear, organized manner, highlighting the dependencies and their respective reasons for removal.

Please help me re-evaluate the dependencies in my current project. For each dependency listed below, provide a detailed assessment of its necessity, including the specific role it plays in the project and any potential impacts of removing it. The dependencies to assess are: [LIST OF DEPENDENCIES]. After your evaluation, suggest which dependencies can be safely removed and explain why, ensuring that the project remains functional and efficient.

Please analyze the current dependency list for the application and identify which packages are essential for its core functionality. Provide a revised list that includes only the necessary dependencies, along with a brief explanation for each package included in the final list. Additionally, highlight any dependencies that can be safely removed and explain why they are not required for optimal performance. Format the output as a clear table with columns for 'Package Name', 'Reason for Inclusion', and 'Reason for Removal'.

Please help me rebuild the application by isolating and removing all unnecessary dependencies. Ensure that the core functionality remains intact and that all features operate as intended after the rebuild. Provide a step-by-step guide detailing the changes made, the rationale behind removing each dependency, and any testing procedures to confirm that the application functions correctly. Additionally, include any potential impacts on performance or user experience due to these changes.

Please create a detailed log of all dependency changes made in the project. For each change, include the name of the dependency, whether it was added or removed, and provide a clear justification for each action taken. Additionally, categorize the changes by type (e.g., security updates, performance improvements, deprecated dependencies) and include the date of each change. Format the log in a table with columns for dependency name, action, justification, category, and date to ensure clarity and organization.

Please execute the full test suite for the application to verify that it functions correctly after the removal of unnecessary dependencies. Provide a detailed report of the test results, including any passed and failed tests, along with relevant error messages or issues encountered during the testing process. Additionally, summarize any areas that may require further attention or debugging based on the results.

Please verify the functionality of all requested features after the recent dependency cleanup. Provide a detailed report that includes: a list of each feature tested, the expected behavior versus the actual behavior observed, any discrepancies found, and recommendations for further action if any features are not functioning correctly. Additionally, include any relevant notes on the testing process and the environment in which the tests were conducted.

Please provide the updated list of dependencies for the project. Ensure that all packages included are necessary for the functionality of the application. Highlight any packages that were removed and explain why they were deemed unnecessary. Additionally, confirm that the current list meets the project's requirements and is optimized for performance.

Please recreate the scenario that led to the introduction of unnecessary dependencies in the project. Outline the specific steps taken during the original implementation, including any configurations, libraries, or code snippets used at that time. After reproducing the scenario, verify if the issue with unnecessary dependencies still occurs and provide a detailed report on your findings, including any changes made to resolve the issue and their impact on the project.

Please validate the build process for the project. Run the build and confirm that it completes successfully without any errors. Specifically, check for issues related to missing dependencies and provide a summary of any errors encountered, along with suggestions for resolving them. Additionally, outline the steps taken during the validation process to ensure clarity and reproducibility.

Please create a detailed checklist to follow before adding any new dependencies to a project. The checklist should include criteria such as evaluating the necessity of the dependency for specific features, assessing the impact on project size and performance, checking for security vulnerabilities, and considering the long-term maintenance and community support of the dependency. Additionally, include steps for documenting the rationale for adding each dependency and guidelines for reviewing existing dependencies for potential removal. Format the checklist in a clear, organized manner with bullet points for easy reference.

Please propose a new rule for the CLAUDE.md file that mandates a justification for each new dependency added to the project. The rule should outline the rationale behind the requirement, including the importance of maintaining a lean codebase and minimizing potential security vulnerabilities. Additionally, provide examples of acceptable justifications, such as performance improvements, necessary features, or compliance with industry standards. Format the rule clearly, and include a section for documenting the justification alongside each dependency.

Please insert comments throughout the codebase that emphasize the importance of minimizing unnecessary dependencies. Each comment should clearly explain why reducing dependencies is crucial for maintainability, performance, and security. Include specific examples of potential issues that can arise from excessive dependencies, such as increased complexity or difficulty in updating the code. Ensure that the comments are concise yet informative, making it easy for future developers to understand the rationale behind this practice.

Create a session opener that emphasizes the importance of reviewing existing dependencies in a project before introducing new ones. The opener should include a brief overview of the potential risks associated with unnecessary dependencies, such as increased complexity and maintenance challenges. Additionally, provide a checklist of key questions to consider during the review process, including how the new dependency will impact current functionality and whether it aligns with project goals. Aim for a concise format that can be easily shared with the team to promote best practices.

Create a project convention document that outlines the process for conducting periodic reviews of the dependency list. Specify the frequency of these reviews, such as every sprint or every month, and detail the criteria for evaluating the necessity of each dependency. Include guidelines on how to document the findings from each review and the steps to take if a dependency is deemed unnecessary, such as removing it or replacing it with a more efficient alternative. Ensure the convention promotes accountability among team members and encourages open discussions about dependency management.