feat: add PR Impact Analyzer prompt

[shiv669]

What This Prompt Does

This prompt helps you quickly understand the impact of a pull request before diving into code review. Instead of manually piecing together what changed and why it matters, you get an automated analysis that tells you exactly where to focus your attention.

The prompt uses two extensions working together. First, the GitHub extension pulls all the PR data like file diffs, commits, and metadata. Then the Developer extension takes that raw data and actually analyzes the code changes to figure out what systems are affected, what could break, and what needs careful review.

Why This Integration Works

When you're reviewing a large PR, you need two things. You need the context about what changed, which GitHub provides. But you also need to understand the technical implications of those changes, which requires analyzing the actual code. Thats where Developer comes in.

For example, if someone adds a new Redis dependency in their PR, the GitHub extension sees that package.json changed. But the Developer extension is what notices theres no connection pooling configured and flags it as a risk. The GitHub part fetches the facts, the Developer part understands what those facts mean for your system.

What Makes It Useful

The output is structured specifically for how developers actually review code. You get a quick risk assessment at the top so you know if this needs 15 minutes or an hour. Then it breaks down which systems are affected with actual risk levels, not just generic warnings.

The checklist section gives you specific things to verify before approving, like whether tests exist for the new rate limiter or if the database migration has a rollback plan. These arent vague suggestions like "check the tests" but concrete items tied to the actual changes in the PR.

It also assigns estimated review times and suggests specific reviewers based on what changed. If the PR touches authentication, it knows to loop in your security lead. If theres a database migration, it tags your DevOps team.

How Its Different

Most PR analysis tools just list changed files and line counts. This prompt actually reads the code and understands the architecture. It catches things like hardcoded configuration that should be in environment variables, or missing error handling in critical paths, or new dependencies that need infrastructure setup.

The risk detection isnt based on simple rules. It actually looks at the code patterns. If you add Redis without pooling config, it flags that. If you change auth middleware without adding tests, it catches it. If you introduce a breaking API change without updating docs, it points it out.

Real World Example

Say your teammate opens a PR adding rate limiting. Without this prompt, youd open the PR, see 12 files changed, start reading through the diff trying to figure out what this affects, whether its safe, what could go wrong.

With this prompt, you immediately see that it touches your auth system which is high risk, adds a database migration which needs coordination, and is missing tests for the new rate limiter. You know to spend time on the Redis configuration and make sure theres a rollback plan for the migration. The whole review becomes focused instead of exploratory.

Technical Details

Extensions Used:

• GitHub extension fetches PR metadata, file diffs, commit history, and author info
• Developer extension analyzes code structure, dependencies, test coverage, and architectural patterns

Output Structure:

• Extension integration section showing the workflow
• Quick summary with risk level and stats
• Systems affected breakdown with specific files and risk ratings
• Concrete risks with exact line numbers and fixes
• Review checklist prioritized by importance
• Action items for both author and reviewers
• Time estimates for different review depths

Format:

• Uses emoji risk indicators for quick scanning
• Markdown headers for structure
• Code blocks for diffs and examples
• Checkboxes for actionable items
• Direct file references with line numbers

Closes

Intermediate Prompt Submission issue (closes #4770 once claimed)

Email for Credits

[email protected]

[github-actions]

✅ Recipe Validation Passed

Your recipe(s) are valid and ready for review!

🔍 Next Steps:

1. Our team will review your recipe
2. If approved, we'll run a security scan
3. Once merged, you'll receive $10 in OpenRouter credits (if email provided)

Thanks for contributing to the goose Recipe Cookbook! 🎉

[github-actions]

🔍 Recipe Security Scan Results

✅ Status: APPROVED - All recipes passed security scan

📊 Scan Summary:

• Total recipes scanned: 1

📋 Individual Recipe Results:
✅ Recipe 1: APPROVED (LOW risk)

🔗 View detailed scan results in the workflow artifacts.

[github-actions]

✅ Recipe Validation Passed

Your recipe(s) are valid and ready for review!

🔍 Next Steps:

1. Our team will review your recipe
2. If approved, we'll run a security scan
3. Once merged, you'll receive $10 in OpenRouter credits (if email provided)

Thanks for contributing to the goose Recipe Cookbook! 🎉

[github-actions]

🔍 Recipe Security Scan Results

✅ Status: APPROVED - All recipes passed security scan

📊 Scan Summary:

• Total recipes scanned: 1

📋 Individual Recipe Results:
✅ Recipe 1: APPROVED (LOW risk)

🔗 View detailed scan results in the workflow artifacts.

[github-actions]

✅ Recipe Validation Passed

Your recipe(s) are valid and ready for review!

🔍 Next Steps:

1. Our team will review your recipe
2. If approved, we'll run a security scan
3. Once merged, you'll receive $10 in OpenRouter credits (if email provided)

Thanks for contributing to the goose Recipe Cookbook! 🎉

[github-actions]

🔍 Recipe Security Scan Results

✅ Status: APPROVED - All recipes passed security scan

📊 Scan Summary:

• Total recipes scanned: 1

📋 Individual Recipe Results:
✅ Recipe 1: APPROVED (LOW risk)

🔗 View detailed scan results in the workflow artifacts.

[taniandjerry]

Hi @shiv669 ! Thank you so much for your contribution. Once the tests run, I'll be able to merge your PR. ❤️