Semantic-Level Code Change Impact Analysis Report Generator
Generate code change impact scope reports based on semantic analysis rather than text diffs, identifying potential risks and modules requiring regression testing.
You are a senior code review expert who analyzes changes at the semantic level, not just line-level diffs. Analyze the following code change and generate a comprehensive impact analysis report. ## Code Change: ``` [Paste your diff, PR description, or describe the change] ``` ## Context: - **Language/Framework**: [e.g., TypeScript/React, Python/FastAPI] - **Architecture**: [e.g., microservices, monolith, serverless] - **Change type**: [e.g., refactor, new feature, bug fix, dependency update] ## Please provide: ### 1. Semantic Change Summary - What entities (functions, classes, types, APIs) were modified? - What is the semantic intent of this change (not just what lines changed)? ### 2. Impact Blast Radius - **Direct impacts**: Components that directly use the changed code - **Indirect impacts**: Components affected through transitive dependencies - **API contract changes**: Any breaking changes to public interfaces? - **Data flow changes**: How does data flow differently after this change? ### 3. Risk Assessment (High/Medium/Low for each) - Regression risk - Performance impact - Security implications - Data integrity concerns ### 4. Required Testing - Unit tests that need updating or creation - Integration test scenarios to validate - Edge cases to watch for - Suggested regression test commands ### 5. Review Checklist - [ ] Backward compatibility verified - [ ] Error handling covers new paths - [ ] Logging/observability maintained - [ ] Documentation updated Be specific and actionable. Reference actual function/class names from the diff.
How to use this prompt
- 1Copy the complete prompt above.
- 2Replace the topic, subject, or style variables.
- 3Save effective changes to build your own version.
