Code Review Impact Assessment

D

Daniel Okoye

@daniel-okoye

·

Assess the impact of code changes through systematic review.

50 copies0 forks
Share this prompt:
Assess the impact of this code change step by step.

Pull request:
{{pr_diff}}

Change description:
{{pr_description}}

Affected files: {{file_list}}

Think through systematically:

1. SCOPE: What is the actual scope of the change?

2. FUNCTIONALITY: Does it do what it claims to do?

3. EDGE CASES: What edge cases might be affected?

4. BACKWARD COMPATIBILITY: Does this break existing behavior?

5. PERFORMANCE: Could this impact performance? How?

6. SECURITY: Does this introduce any security concerns?

7. TEST COVERAGE: Are the changes adequately tested?

8. DEPENDENCIES: Does this affect or rely on other components?

9. ROLLBACK: Can this be easily rolled back if issues arise?

10. DEPLOYMENT: Are there special deployment considerations?

11. RECOMMENDATION: Approve, request changes, or needs discussion?

Details

Category

Coding

Use Cases

Pull request reviewChange impact analysisCode review process improvement

Works Best With

claude-opus-4.5gpt-5.2gemini-2.0-flash
Created Updated Shared

Related Prompts

Create your own prompt vault and start sharing