skills.rest
pytholic
pytholicCOMMUNITY
Explore all skills by this author →
𝕏@rh__147GitHub

pr-description

Generate a pull request description from the branch diff and PR template.

2|1|Updated Apr 22, 2026
Search Tags:#code review#pull request#git diff#pr description#branch analysis
One-click install
npx skills add https://github.com/pytholic/claude-skills --skill pr-description-pytholic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-description
Source: https://github.com/pytholic/claude-skills/tree/main/pr-description
Command: npx skills add https://github.com/pytholic/claude-skills --skill pr-description-pytholic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates a minimal, accurate pull request description from the current branch's changes so you can open PRs faster without inventing details.

Core Features & Use Cases

  • Branch-aware diffing: Finds the most likely remote base branch instead of assuming the default branch.
  • Template preservation: Fills the repository's PR template structure while keeping headings and checkbox labels intact.
  • Diff-first summarization: Uses the branch diff as the source of truth, with commit history only as supporting context.
  • Use Case: After finishing a code change, generate a ready-to-paste PR title and body that match the repo's conventions.

Quick Start

Ask for a PR description for the current branch using the repository's template and the actual diff.

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 pull request description from a git diff?▼

To generate a pull request description from a git diff, the Skill inspects the current branch changes and commit history to produce a ready-to-paste PR summary. It uses the branch diff as the primary source of truth for accurate content.

Can I automatically fill my repository PR template using branch changes?▼

Yes, you can automatically fill your repository PR template using branch changes. The Skill preserves existing template headings and checkbox labels while injecting summarized diff content into the appropriate sections.

How does branch-base detection work when creating PR summaries?▼

Branch-base detection for PR summaries works by finding the most likely remote base branch instead of assuming the default branch. This ensures the evaluated diff accurately reflects only your current branch changes.

What is the best way to write a PR summary after refactoring code?▼

The best way to write a PR summary after refactoring code is using a diff-first summarization approach. The Skill analyzes the actual branch diff alongside commit-log context to generate concise descriptions matching repo conventions.

Does the generated PR description rely on commit history or the actual diff?▼

The generated PR description relies primarily on the actual diff rather than just commit history. Commit logs are used only as supporting context to ensure the pull request summary accurately reflects the implemented changes.

Related Skills

Explore More Software Engineering Skills→
n24q02mn24q02m
3

review-pr

Analyze all commits against the base branch to detect breaking changes and assess blast radius.

Community
Advanced
marcioaltoemarcioaltoe
14

git-pr-creation

Create a GitHub pull request from the current branch into dev with a structured body.

Community
Advanced
adityasingh2400adityasingh2400
2

review

Analyze pull request diffs against the base branch for SQL safety and structural risks.

Community
Advanced
paulchiupaulchiu
3

write-pull-request

Generate pull request descriptions from git diff and commit history.

Community
Intermediate