skills.rest
timurgaleev
timurgaleevCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pr-summary

Analyze pull request commits and files to generate structured descriptions.

5|Updated Apr 24, 2026
Search Tags:#automation#git#commits#diff#summary#code-review#pull-request
One-click install
npx skills add https://github.com/timurgaleev/vibestack --skill pr-summary-timurgaleev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-summary
Source: https://github.com/timurgaleev/vibestack/tree/main/skills/pr-summary
Command: npx skills add https://github.com/timurgaleev/vibestack --skill pr-summary-timurgaleev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generate precise PR descriptions by analyzing all commits and file changes, eliminating manual drafting and reducing review friction.

Core Features & Use Cases

  • Analyze all commits in a PR to capture the complete change history.
  • Preserve existing notes in the PR body while adding a structured, reviewer-friendly summary.
  • Produce concise, actionable summaries for faster reviews across teams.

Quick Start

Summarize the current PR by number or on the active branch to update its description.

Frequently Asked Questions about pr-summary

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

FAQPage Schema
How do I automatically generate a pull request description from git commits?▼

To generate a pull request description, the skill analyzes all git commits and file changes in the PR to produce an accurate, comprehensive summary. It reads the full PR context and updates the description automatically, eliminating manual drafting.

Can I update a PR summary without losing existing review notes?▼

Yes, you can update a PR summary without losing existing notes. The skill preserves the existing PR body content while appending a structured, reviewer-friendly summary of the code changes, ensuring previous context remains intact for the team.

What is the best way to summarize code changes across multiple commits for a code review?▼

The best way to summarize code changes for a review is to analyze the complete change history across all commits and files. This captures the full context, producing concise, actionable summaries that reduce review friction and speed up team workflows.

Does this PR summary tool work with complex diffs containing multiple changed files?▼

Yes, the PR summary tool works with complex diffs containing multiple changed files. It explicitly analyzes review workflows where multiple commits and files exist, reading the full PR context to produce a precise, actionable description of the changes.

How do I refresh a stale pull request description to match the latest branch changes?▼

To refresh a stale pull request description, you can summarize the PR by its number or active branch. The skill reads the latest commits and file diffs to generate an updated, structured summary that accurately reflects the current state of the code.

Related Skills

Explore More Software Engineering Skills→
getlargegetlarge

github

Automate GitHub operations using the gh CLI for issues, PRs, and CI status.

Community
Intermediate
tribedotruntribedotrun
8

mando-pr-summary

Generate an ASCII PR summary diagram and reviewer checklist for GitHub pull requests.

Official
Advanced
SAPSAP
294

review-pr

Review pull requests against Angular 21+ conventions and checklist.

Official
Advanced
EpicenterHQEpicenterHQ
4.7k

git

Prompts users for required infoGit push commits and generates commit messages adhering to formatting and linting conventions.

Official
Advanced