What input is required?

A PR number is passed as the argument (see [pr-number]).

What does the output look like?

A structured PR Summary with sections: Overview, Key Changes, Risks, and Recommendations.

Can I customize or extend what is reported?

Yes. The skill uses gh pr commands and formats into a standard layout; you can add more sections or fields as needed.

pr-summary

npx machina-cli add skill fusengine/agents/pr-summary --openclaw

Files (1)

SKILL.md

1.0 KB

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:

Overview - What does this PR do?
Key Changes - Main files and modifications
Potential Risks - Breaking changes, security concerns
Review Recommendations - What to check carefully

Output Format

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

Source

git clone https://github.com/fusengine/agents/blob/main/plugins/ai-pilot/skills/pr-summary/SKILL.mdView on GitHub

Overview

Analyzes the current pull request by aggregating the diff, comments, and changed files to produce a concise summary. It helps reviewers quickly understand what changed and what to check before merging.

How This Skill Works

It gathers data using gh pr diff for the patch, gh pr view --comments for discussion, and gh pr diff --name-only for the changed files, then formats the results into the standardized PR Summary layout. The output includes sections for Overview, Key Changes, Risks, and Recommendations to streamline reviews.

When to Use It

When reviewing PRs before merging to get a concise snapshot.
During code review to quickly identify key changes and impacted areas.
When sharing PR status with stakeholders who need a high-level view.
For triaging PRs with large diffs or many changed files.
When verifying alignment with project goals and security guidelines.

Quick Start

Step 1: Run the skill with a pr-number to fetch diff, comments, and file changes.
Step 2: Review the generated PR Summary for Overview, Key Changes, and Risks.
Step 3: Apply the Recommendations to guide your merge decision and follow-up tests.

Best Practices

Verify the PR number passed as an argument matches the PR you are reviewing.
Cross-check the Key Changes against the PR description for consistency.
Review the list of changed files to ensure no unintended modules were touched.
Pay attention to Potential Risks and Security concerns highlighted in the summary.
Use the Recommendations to guide the merge decision and plan follow-up testing.

Example Use Cases

PR Summary: Add OAuth login with session management.
PR Summary: Refactor user service into microservices and update interfaces.
PR Summary: Update API endpoints; rename fields and deprecate old ones.
PR Summary: Improve test coverage; add integration tests for billing.
PR Summary: Fix input sanitization to close a security vulnerability.

Frequently Asked Questions

Add this skill to your agents