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-summary

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.0 KB
---
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`

Overview

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.

How this skill works

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.

When to use it

  • Reviewing a pull request before assigning reviewers
  • Preparing a PR for merge to ensure no blockers remain
  • On-boarding a reviewer who needs a quick, high-level view
  • Auditing changes for security or compatibility risks
  • Automated checks in CI that produce human-readable summaries

Best practices

  • Run the skill after tests and CI checks complete to include current status
  • Keep PR descriptions clear so the summary can reflect author intent
  • Use the summary to drive targeted code review comments rather than broad requests
  • Verify suggested risks against local runs or unit tests for confirmation
  • Include links to relevant files or comments in the PR for easy navigation

Example use cases

  • Generate a short summary for a large feature PR to guide reviewers
  • Quickly spot potential breaking API changes in a refactor before merging
  • Produce an executive-friendly summary for stakeholders showing impact and risks
  • Automate posting a digest of opened PRs to a team channel with highlights
  • Use as a pre-merge checklist to confirm tests, docs, and changelog updates

FAQ

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.