pr-summary

Summarize GitHub pull requests using live diffs, comments, and metadata from the gh CLI.

1|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/jimmymalhan/codereview-pilot --skill pr-summary-jimmymalhan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-summary
Source: https://github.com/jimmymalhan/codereview-pilot/tree/main/.claude/skills/pr-summary
Command: npx skills add https://github.com/jimmymalhan/codereview-pilot --skill pr-summary-jimmymalhan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the process of summarizing pull requests, providing key information for efficient code review.

Core Features & Use Cases

  • Automated Summarization: Generates a concise summary of changes, risks, and verification steps for a given pull request.
  • Contextual Information: Fetches live PR data including diff, comments, and metadata using the GitHub CLI.
  • Use Case: Before merging a pull request, use this skill to quickly get an overview of what has changed, identify potential risks, and understand how to verify the changes.

Quick Start

Use the pr-summary skill to summarize pull request number 123.

Frequently Asked Questions about pr-summary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I summarize a GitHub pull request for code review?

To summarize a GitHub pull request, this skill fetches live diffs, comments, and metadata using the gh CLI. It identifies changes, scope, risk areas, and verification steps so you can review code efficiently before merging.

What does an automated PR summary include?

An automated PR summary includes a concise overview of changes, potential risk areas, and verification steps. It fetches live data including diffs, comments, and metadata from GitHub to provide full context for code review.

Can I summarize the current branch's pull request without a PR number?

Yes, you can summarize the current branch context without specifying a PR number. The skill supports both specific PR numbers and the current branch context to fetch live diffs, comments, and metadata.

Do I need the GitHub CLI to summarize pull requests?

Yes, the GitHub CLI is required to summarize pull requests. The skill fetches live diff, comment, and metadata data using the gh CLI to generate a summary of changes, risks, and verification steps.

What's the best way to identify risk areas before merging a pull request?

The best way to identify risk areas before merging is to use an automated PR summary. This skill fetches live diffs and metadata using the gh CLI to highlight changes, scope, risk areas, and verification steps for efficient code review.

How does fetching live PR data improve code review?

Fetching live PR data improves code review by providing real-time diffs, comments, and metadata from GitHub. This allows the summary to accurately identify current changes, scope, risk areas, and verification steps before merging.