skills.rest
v1-io
v1-ioOFFICIAL
Explore all skills by this author →
WebsiteGitHub

pr-description

Generate PR descriptions from git diff and commit history.

6|2|Updated Jan 15, 2026
Search Tags:#automation#git#github#pr#description#pull-request
One-click install
npx skills add https://github.com/v1-io/v1tamins --skill pr-description-v1-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-description
Source: https://github.com/v1-io/v1tamins/tree/main/claude/skills/pr-description
Command: npx skills add https://github.com/v1-io/v1tamins --skill pr-description-v1-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill generates a comprehensive PR description from the changes in a branch, saving time and ensuring consistent documentation.

Core Features & Use Cases

  • Auto-summarizes changes with git diff and commit history to produce a concise, informative PR body
  • Generates a structured PR description including a summary of changes, testing notes, and related issues
  • Use Case: When preparing PRs for feature branches, bug fixes, or refactors, ensure PR bodies are complete and standardized

Quick Start

Provide the PR URL or number to generate its description.

Frequently Asked Questions about pr-description

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

FAQPage Schema
How do I auto-generate a PR description from git diff and commit history?▼

To auto-generate a PR description, provide the PR URL or number to the Skill. It analyzes git diff and git log to summarize code changes, then uses GitHub CLI to update the pull request body.

Can I update an existing GitHub PR body to reflect the latest branch changes?▼

Yes, you can update an existing GitHub PR body to reflect latest changes. The Skill leverages the GitHub CLI to push the newly generated summary of code changes directly to the current pull request.

What is the best way to standardize pull request descriptions for refactoring branches?▼

The best way to standardize pull request descriptions is auto-generating a structured PR body. It summarizes changes, adds testing notes, and references related issues by analyzing commit history from your feature or refactor branch.

Does this PR generation method require the GitHub CLI to update pull requests?▼

Yes, updating pull request content requires the GitHub CLI. While the description generation itself relies on reading git diff and git log, the CLI is used to apply the structured summary directly to the GitHub pull request.

What information is included in an auto-generated pull request description?▼

An auto-generated pull request description includes a structured summary of code changes, testing notes, and related issues. It derives this information directly from the git diff and commit history of the target branch.

When should I use automated PR description generation instead of writing manually?▼

You should use automated PR description generation when preparing pull requests for feature branches, bug fixes, or refactors. It ensures consistent documentation and saves time by summarizing commit history into a standardized PR body.

Related Skills

Explore More Software Engineering Skills→
RanFRRanFR
2

pr-creator

Automates GitHub Pull Request creation using Git CLI and gh auth workflows.

Community
Intermediate
diShine-digital-agencydiShine-digital-agency
1

shine-ship

Automate the ship cycle from branch creation to merged pull request.

Community
Intermediate
shekerkammashekerkamma

ship

Automate git-based code shipping with tests, versioning, and pull requests.

Community
Advanced
arowinskiarowinski

pr

Create pull requests with titles and template-aligned bodies from git diffs.

Community
Intermediate