pr-summary
starsforks
How to install pr-summary?
fusengine/agents/pr-summary
$npx -y skills add fusengine/agents --skill pr-summarySummarize current pull request with diff, comments, and changed files. Use when reviewing PRs or before merging.
SKILL.md
| 1 | # PR Summary Skill |
| 2 | |
| 3 | Summarize the current pull request. |
| 4 | |
| 5 | ## Pull Request Context |
| 6 | |
| 7 | - **PR diff:** !`gh pr diff` |
| 8 | - **PR comments:** !`gh pr view --comments` |
| 9 | - **Changed files:** !`gh pr diff --name-only` |
| 10 | - **PR status:** !`gh pr status` |
| 11 | |
| 12 | ## Task |
| 13 | |
| 14 | Analyze this pull request and provide: |
| 15 | |
| 16 | 1. **Overview** - What does this PR do? |
| 17 | 2. **Key Changes** - Main files and modifications |
| 18 | 3. **Potential Risks** - Breaking changes, security concerns |
| 19 | 4. **Review Recommendations** - What to check carefully |
| 20 | |
| 21 | ## Output Format |
| 22 | |
| 23 | ```markdown |
| 24 | ## PR Summary: [Title] |
| 25 | |
| 26 | ### Overview |
| 27 | [1-2 sentences] |
| 28 | |
| 29 | ### Key Changes |
| 30 | - [file]: [change description] |
| 31 | - ... |
| 32 | |
| 33 | ### Risks |
| 34 | - [risk if any] |
| 35 | |
| 36 | ### Recommendations |
| 37 | - [what to verify] |
| 38 | ``` |
| 39 | |
| 40 | ## Debug |
| 41 | |
| 42 | - Session: ${CLAUDE_SESSION_ID} |
| 43 | - Timestamp: !`date +%Y-%m-%d_%H:%M:%S` |
People who liked this also viewed
6 picksType
- requesting-code-reviewUse when completing tasks, implementing major features, or before merging to verify work meets requirementsSkillsJul 2026
- code-reviewSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- receiving-code-reviewUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performativeSkillsJul 2026
- baoyu-format-markdownFormats plain text or markdown files with frontmatter, titles, summaries, headings, bold, lists, and code blocks. Use when user asks to "format markdown", "beautify article", "add formatting", or imprSkillsJul 2026
- code-review-excellenceMaster effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing reSkillsJul 2026
- code-review-and-qualityConducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensiSkillsJul 2026
