pr-description

Generate PR descriptions from commit history and changed files.

Updated Aug 23, 2026

Search Tags:#automation #git #documentation #code-review #commit-history #pr-description

Ready to run

npx skills add https://github.com/overthestream/agent-dotfile --skill pr-description-overthestream

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-description
Source: https://github.com/overthestream/agent-dotfile/tree/main/claude/skills/pr-description
Command: npx skills add https://github.com/overthestream/agent-dotfile --skill pr-description-overthestream

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating PR descriptions from commit history and file changes is time-consuming and error-prone when done manually, leading to inconsistent PR bodies.

Core Features & Use Cases

Analyze commit history to summarize changes and detect scope.
Inspect changed files and reference docs to craft coherent narratives.
Optionally save a PR_DESCRIPTION.md or display the description for easy paste into PR bodies.

Quick Start

Run the pr-description workflow on your current branch to generate a PR description automatically.

Frequently Asked Questions about pr-description

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

FAQPage Schema

How do I generate a PR description from git commit history automatically?▼

Generate PR descriptions by running the workflow on your current branch to analyze commit history and changed files. It produces summaries suitable for PR bodies, categorizing changes and extracting issue references.

What is the best way to summarize code review changes from multiple commits?▼

Summarize code review changes by inspecting commit history and changed files to craft coherent narratives. This detects scope and applies to features, bugfixes, and doc updates across current branches.

Can I save generated PR descriptions to a markdown file instead of copying them manually?▼

You can save generated PR descriptions to a PR_DESCRIPTION.md file. Alternatively, the workflow can display the description directly for easy pasting into PR bodies.

Does generating PR documentation from commits work for bugfixes and doc updates?▼

Generating PR documentation from commits works for bugfixes and doc updates. The workflow analyzes changed files and commit history to categorize changes and produce summaries for these branch types.

How do I extract issue references from commit history into a PR body?▼

Extract issue references by analyzing commit history to detect and include them in the generated PR description. The workflow supports extracting these references while categorizing branch changes.