pr-description

Update GitHub PR descriptions from commits and diffs.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/Nabilhassan12345/voice-ai-workspace --skill pr-description-nabilhassan12345
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-description
Source: https://github.com/Nabilhassan12345/voice-ai-workspace/tree/main/pipecat/.claude/skills/pr-description
Command: npx skills add https://github.com/Nabilhassan12345/voice-ai-workspace --skill pr-description-nabilhassan12345

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Update GitHub PR descriptions to reflect changes, reducing manual editing and ensuring accurate summaries for reviewers.

Core Features & Use Cases

  • Auto-generate or update PR descriptions by aggregating PR title, base branch, commits, and diffs.
  • Incorporate provided --fixes numbers from arguments or commit messages (e.g., Fixes #123) and populate closing notes for linked issues.
  • Identify breaking changes or notable changes and produce a coherent narrative suitable for reviewers.
  • Use Case: When reviewing feature branches with multiple commits, auto-summarize changes for faster approval.

Quick Start

Update the current PR description to reflect the latest commits and changes using the /pr-description command.

Frequently Asked Questions about pr-description

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

FAQPage Schema
How do I automatically generate a GitHub PR description from commits?

To generate a GitHub PR description automatically, this Skill parses PR metadata, collects commits via `git log main..HEAD`, and analyzes the diff to construct a concise summary of changes for reviewers.

Can I automatically link and close GitHub issues in my pull request description?

Yes, you can automatically link and close GitHub issues by passing `--fixes` arguments or including closing keywords like "Fixes #123" in your commit messages, which the tool extracts to populate the PR notes.

Does this PR summarization tool work with feature, bugfix, and refactor branches?

This PR summarization tool works across open pull requests handling feature, bugfix, and refactor branches, reading the `git diff main..HEAD` to identify notable changes and produce a coherent narrative.

What is the best way to update an existing pull request description to reflect new commits?

The best way to update an existing pull request description is to run the `/pr-description` command, which aggregates the latest commits and diffs to overwrite the description with an accurate, reviewer-friendly summary.

Do I need to manually write breaking change notes or will the PR summary tool detect them?

You do not need to manually write breaking change notes; the tool automatically analyzes your commit history and diffs to identify breaking or notable changes and incorporates them into the PR description.