impact-analysislisted

# Impact Analysis Skill Analyze the impact of a proposed change on the codebase. ## When to Use This skill auto-activates when: - User asks "what will be affected if I change X?" - User wants to understand change impact before implementing - User mentions "impact", "affected", or "dependencies" - User is planning a significant change or refactoring ## Workflow 1. **Understand the change** - Parse description for change details - If file path provided, read the file - Identify: - What is being changed? - Why is it being changed? - What is the expected outcome? 2. **Map dependencies** - Call `analyze_project_references(solution_or_dir)` - Call `map_dotnet_structure(root)` - Use Grep to find usages of changed component 3. **Identify affected areas** ### Direct Impact - Files that directly use the changed component - Projects that reference the changed project - Tests that test the changed code ### Indirect Impact - Code that depends on affected code - Downstream consumers - Configuration that references changed items 4. **Analyze by change type** #### API Change (Breaking) ``` Method signature change: IService.GetUser(int id) → GetUser(Guid id) Direct Impact: - All callers of GetUser() - Integration tests - API clients Files Affected: - UserController.cs (line 45) - UserService.cs (line 23) - UserServiceTests.cs (lines 12, 34, 56) ``` #### Schema Change (Database) ```