Pull request context
- •PR metadata: !
gh pr view --json title,body,author,baseRefName,headRefName,additions,deletions,changedFiles - •PR diff: !
gh pr diff - •PR comments: !
gh pr view --comments - •Changed files: !
gh pr diff --name-only
Your task
Analyze this pull request and provide a comprehensive summary:
1. Overview
- •What is this PR trying to accomplish?
- •What problem does it solve or feature does it add?
2. Changes breakdown
- •Group changes by category (e.g., features, fixes, refactoring, tests, docs)
- •Highlight the most significant changes
- •Note any deleted or deprecated code
3. Impact analysis
- •What parts of the codebase are affected?
- •Are there any breaking changes?
- •What dependencies or downstream systems might be impacted?
4. Review guidance
- •What areas deserve the closest review?
- •Are there any potential concerns or risks?
- •What tests or validations should be performed?
5. One-line summary
- •Provide a concise summary suitable for release notes or changelog
Keep the summary scannable with bullet points. Focus on the "why" and "what", not just listing files changed.