| name | pr-summary |
| description | Generate a comprehensive Pull Request summary with risk assessment. Use when user says "PR summary", "summarize PR", "review pull request", or provides a PR number. Classifies changes, assesses risks, and identifies review focus areas. |
| user-invocable | true |
| allowed-tools | Read, Grep, Glob, Bash |
| argument-hint | [pr-number] |
Pull Request Context
- PR metadata: !
gh pr view $ARGUMENTS --json title,body,author,baseRefName,headRefName,additions,deletions,changedFiles,labels,reviewRequests 2>/dev/null || echo "Please specify a valid PR number"
- PR diff: !
gh pr diff $ARGUMENTS 2>/dev/null || echo "No diff available"
- PR comments: !
gh pr view $ARGUMENTS --comments 2>/dev/null || echo ""
- PR checks: !
gh pr checks $ARGUMENTS 2>/dev/null || echo "No checks"
- Linked issues: !
gh pr view $ARGUMENTS --json body 2>/dev/null | grep -oE '#[0-9]+' || echo "None"
Analysis Tasks
1. Change Classification
Categorize this PR:
- Type: feature / bugfix / refactor / docs / test / chore / security
- Scope: Which modules/components are affected
- Size: S (< 50 lines) / M (50-200) / L (200-500) / XL (500+)
2. PR Title Generation
Generate a concise, descriptive PR title in English (under 70 characters). Follow Conventional Commits format: <type>: <description>.
3. Change Summary
- What problem does this PR solve?
- What approach was taken?
- What are the key implementation decisions?
4. Risk Assessment
| Risk Factor | Level | Details |
|---|
| Breaking changes | LOW/MED/HIGH | [details] |
| Security impact | LOW/MED/HIGH | [details] |
| Performance impact | LOW/MED/HIGH | [details] |
| Test coverage | LOW/MED/HIGH | [details] |
| Rollback difficulty | LOW/MED/HIGH | [details] |
5. Review Focus Areas
Identify the most critical files/sections that reviewers should focus on, with specific line references and reasoning.
6. Missing Items Check
Output Format
Output the summary directly as rendered markdown (NOT inside a code block). Use the following structure:
PR Summary
Suggested Title: <type>: <English description under 70 chars>
| Field | Value |
|---|
| Type | feature / bugfix / refactor / docs / test / chore / security |
| Scope | affected modules/components |
| Size | S / M / L / XL |
What
1-2 sentence description of what this PR does.
Why
1-2 sentence description of the problem being solved.
How
Key implementation decisions and approach taken.
Risk Assessment
| Risk Factor | Level | Details |
|---|
| Breaking changes | LOW/MED/HIGH | details |
| Security impact | LOW/MED/HIGH | details |
| Performance impact | LOW/MED/HIGH | details |
| Test coverage | LOW/MED/HIGH | details |
| Rollback difficulty | LOW/MED/HIGH | details |
Review Focus Areas
| File | Lines | Reason |
|---|
path/to/file.ts | L10-L25 | reason to focus here |
path/to/file.ts | L42 | reason to focus here |
Checklist
IMPORTANT: Output as rendered markdown directly. Do NOT wrap the output in a code fence.
