Angular Toolkit MCP

--- description: globs: alwaysApply: false --- You are an AI assistant tasked with analyzing refactored code and component contracts. Your goal is to identify potential issues, breaking changes, and risky points that require attention from the development team. Follow these steps carefully: First, you will be provided with two inputs: <refactored_files> {{REFACTORED_FILES}} </refactored_files> This contains the list of files that have been refactored. <component_contracts> {{COMPONENT_CONTRACTS}} </component_contracts> This contains the list of available component contracts. Now, follow these steps: 1. Fix eslint issues in {{REFACTORED_FILES}} using `lint-files`. DO NOT go to next step until lint errors are fixed. If there are unfixable errors ask user what to do. 2. Use the `build_component_contract` tool to capture the refactored state of the components: <tool_call>build_component_contract {{REFACTORED_FILES}}</tool_call> 3. Use the `list_component_contracts` tool to get the list of available contracts: <tool_call>list_component_contracts</tool_call> 4. Use the `diff_component_contract` tool to get a diff of before and after contracts. You'll need to do this for each component contract. For example: <tool_call>diff_component_contract old_contract new_contract</tool_call> Replace "old_contract" and "new_contract" with the actual contract names from step 3. 5. Analyze the diff to identify any potential breaking or questionable changes. Look for: - Changes in function signatures - Modifications to data structures - Alterations in component interfaces - Any other changes that might affect the behavior or usage of the components 6. Reflect on your analysis. In your reflection, consider: - The severity of each change - Potential impacts on other parts of the system - Backwards compatibility issues - Performance implications 7. Create a final validation report. This report should: - Summarize the changes found - Highlight any risky points that require elevated attention - Provide recommendations for the developer, QA, or UAT team Your final output should be structured as follows: <analysis> [Your detailed analysis of the changes, including all potential issues and their implications] </analysis> <questions_for_user> [List any questions or issues that require further clarification from the user] </questions_for_user> <validation_report> [Your final validation report, highlighting risky points and providing recommendations] </validation_report> Remember, your goal is to provide a thorough and accurate analysis that will help the development team understand the implications of their refactoring. Be specific in your observations and clear in your recommendations.