pr-description

Generate GitHub PR descriptions with Summary and Fixes sections from commits and diffs.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/Gorillaa-ai-org/pipecat --skill pr-description-gorillaa-ai-org
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-description
Source: https://github.com/Gorillaa-ai-org/pipecat/tree/main/.claude/skills/pr-description
Command: npx skills add https://github.com/Gorillaa-ai-org/pipecat --skill pr-description-gorillaa-ai-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Update a GitHub PR description with a summary of changes

Core Features & Use Cases

  • Generate a standardized PR description from commit messages and diffs
  • Include related issues from the --fixes argument or commit messages (e.g., "Fixes #123")
  • Produce a consistent format with Summary, Testing, and Fixes sections

Quick Start

Provide the PR number and optional fixes to update the PR description.

Frequently Asked Questions about pr-description

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

FAQPage Schema
How do I automate GitHub PR description updates with commit summaries?

You can automate GitHub PR description updates by analyzing commit messages and diffs to generate a structured summary. This process extracts changes and issue references to construct a ready-to-use description block.

Can I generate a standardized PR description from diffs automatically?

Yes, you can generate a standardized PR description from diffs automatically. The system analyzes PR details and commits to produce a consistent format with Summary, Testing, and Fixes sections.

Does this PR update tool require special GitHub access tokens?

No, this PR update tool requires zero special access. It directly analyzes your PR details, commits, and diffs to output a ready-to-use description block without needing elevated permissions.

How do I include related issue references in an automated PR summary?

You can include related issue references in an automated PR summary by using a fixes argument or parsing commit messages. It detects patterns like Fixes #123 to populate the description block.

What is the best way to format commit messages for automated PR summaries?

The best way to format commit messages for automated PR summaries is to include clear change descriptions and issue references. The system parses these details to build structured Summary and Fixes sections.

Why are my GitHub PR descriptions missing structured testing sections?

GitHub PR descriptions miss structured testing sections when not using an automated summarization tool. This skill analyzes diffs and commits to consistently populate Summary, Testing, and Fixes blocks.