home / skills / fusengine / agents / pr-summary
This skill summarizes a pull request by analyzing diff, comments, and changed files to deliver a concise review overview.
npx playbooks add skill fusengine/agents --skill pr-summaryReview the files below or copy the command above to add this skill to your agents.
---
name: pr-summary
description: Summarize current pull request with diff, comments, and changed files. Use when reviewing PRs or before merging.
argument-hint: "[pr-number]"
context: fork
agent: fuse-ai-pilot:explore-codebase
disable-model-invocation: true
user-invocable: true
---
# PR Summary Skill
Summarize the current pull request.
## Pull Request Context
- **PR diff:** !`gh pr diff`
- **PR comments:** !`gh pr view --comments`
- **Changed files:** !`gh pr diff --name-only`
- **PR status:** !`gh pr status`
## Task
Analyze this pull request and provide:
1. **Overview** - What does this PR do?
2. **Key Changes** - Main files and modifications
3. **Potential Risks** - Breaking changes, security concerns
4. **Review Recommendations** - What to check carefully
## Output Format
```markdown
## PR Summary: [Title]
### Overview
[1-2 sentences]
### Key Changes
- [file]: [change description]
- ...
### Risks
- [risk if any]
### Recommendations
- [what to verify]
```
## Debug
- Session: ${CLAUDE_SESSION_ID}
- Timestamp: !`date +%Y-%m-%d_%H:%M:%S`
This skill summarizes the current pull request by aggregating the diff, comments, changed files, and PR status into a concise, actionable report. It helps reviewers and maintainers quickly understand scope, risks, and verification steps before merging. The skill is implemented in TypeScript and designed for integration with agent workflows.
The skill inspects the PR diff, file list, and comment threads to extract intent and key modifications. It highlights main changed files, potential breaking changes, and security concerns, then produces targeted review recommendations. It reads PR status to surface merge blockers and uses CLI queries to gather up-to-date context.
What inputs does the skill require?
It requires access to the PR diff, comments, changed file list, and PR status to produce a complete summary.
Can it detect security or breaking changes automatically?
It flags likely risks based on code patterns and file types but recommends manual verification and test runs for confirmation.
How does it surface reviewer actions?
The summary includes concise recommendations and specific files or lines to inspect, making it clear what to verify during review.