pr-summary

Generate concise pull request summaries from branch diffs and git history.

8|1|Updated Mar 14, 2026

Search Tags:#git #code review #pull request #branch #pr #summary

Ready to run

npx skills add https://github.com/Olatisunkanmi/claudefiles --skill pr-summary-olatisunkanmi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-summary
Source: https://github.com/Olatisunkanmi/claudefiles/tree/main/skills/pr-summary
Command: npx skills add https://github.com/Olatisunkanmi/claudefiles --skill pr-summary-olatisunkanmi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns branch diffs into a clear, reviewer-ready pull request description, removing the manual effort of summarizing changes and impacts.

Core Features & Use Cases

Overview generation: Produce a short description of the pull request purpose and intent.
Key changes extraction: Summarize added features, bug fixes, and refactors from commit and diff data.
Impact, issues, and testing guidance: Explain project impact, reference related issues or discussions, and list suggested testing steps.
Use Case: Prepare a PR description for reviewers when opening a feature branch merge request, or generate changelog entries during release preparation.

Quick Start

Generate a concise PR summary for the current branch compared to the default branch and save it as a markdown file named with the branch and the current date and time.

Frequently Asked Questions about pr-summary

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

FAQPage Schema

How do I generate a pull request summary from git branch diffs automatically?▼

To generate a pull request summary, the Skill analyzes git branch diffs and commit history compared to the default branch, producing an overview, key changes, impact assessment, and testing guidance. It outputs a markdown file named with the branch and timestamp.

What is included in an automated PR description for a feature branch?▼

An automated PR description includes a short overview of the intent, extracted key changes such as features and bugfixes, an impact assessment, related issues, and suggested testing steps derived from commit and diff data.

Can I use branch diffs to create changelog entries for release preparation?▼

Yes, you can use branch diffs to create changelog entries. By summarizing commits, file changes, and bugfix scopes against the default branch, the Skill generates markdown content suitable for release notes and changelogs.

Does the pull request summary detect the default branch automatically?▼

Yes, the pull request summary detects the default branch automatically. It uses the repository git history to identify the default branch and compares the current feature branch diffs against it to generate the summary.

What's the best way to prepare reviewer notes from git commit history?▼

The best way to prepare reviewer notes is to use a Skill that parses git commit history and file diffs to summarize feature scopes, impacts, and testing guidance. This removes manual effort and outputs a reviewer-ready markdown file.