pr-review-prlisted
Install: claude install-skill tony/ai-workflow-plugins
# Review PR Description
Evaluate an existing PR description against gold-standard patterns and suggest concrete improvements.
Target PR: $ARGUMENTS
---
## Procedure
### 1. Fetch the PR
- If `$ARGUMENTS` contains a PR number (e.g., `#42`, `42`) or URL, use it directly
- If `$ARGUMENTS` is empty, detect the current branch's PR:
```
gh pr view --json number,title,body,url
```
- Fetch the full PR details:
```
gh pr view <number> --json title,body,url
```
### 2. Fetch the Diff Context
- Get the PR diff to understand the scope of changes:
```
gh pr diff <number>
```
- Count files changed and estimate the magnitude (small fix, medium feature, large overhaul)
- This context is needed to judge whether the description is **proportional** to the change
- If the user's message names a PR template, read it and use its sections as the structural baseline for the evaluation below. Use it silently — this command reports findings and never raises template questions
### 3. Evaluate Against Quality Patterns
Check each applicable dimension. Not every dimension applies to every PR — a one-line typo fix doesn't need a Design Decisions section.
| Dimension | What to check |
|---|---|
| **Structure** | Does it use `## Summary`, `## Changes`, `## Test plan` headings where appropriate for the change size? |
| **Proportionality** | Is the detail level proportional to the diff size? Small fix shouldn't have 20 bullets; large feature shouldn't be one sentence. |
| **Bold impa