pr-description

Generate conventional commit-style titles and concise descriptions for GitHub Pull Requests.

4|3|Updated Jul 14, 2025

Search Tags:#automation #git #code review #pull request #commit #github

Ready to run

npx skills add https://github.com/luan/dot-claude --skill pr-description-luan

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of clear and informative titles and descriptions for your GitHub Pull Requests, saving you time and ensuring consistency.

Core Features & Use Cases

Contextual Title Generation: Creates titles following conventional commit standards (type(scope): description).
Automated Body Summarization: Generates a concise explanation of the changes based on commit history and diffs.
Edge Case Handling: Manages scenarios with uncommitted changes, untracked files, or no new commits.
Use Case: After completing a feature, run this skill to automatically draft a PR title like feat(auth): implement two-factor authentication and a body explaining the motivation and approach.

Quick Start

Update the PR title and description using the current branch context.

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 pull request title and description from my current branch?▼

To generate a pull request title and description automatically, this Skill retrieves branch context using Git commands and GitHub CLI. It then creates conventional commit-style titles and concise prose summaries based on your commit history and diffs.

Can I generate conventional commit-style PR titles from uncommitted changes?▼

Yes, you can generate conventional commit-style PR titles from uncommitted changes. This Skill handles various edge cases including untracked files, uncommitted modifications, and scenarios where no new commits exist on your branch.

What's the best way to write descriptions for stacked pull requests in GitHub?▼

The best way to write descriptions for stacked pull requests is to use a tool that understands branch context. This Skill specifically manages stacked PRs by analyzing the commit history and diffs to produce accurate, concise prose explanations.

Do I need the GitHub CLI installed to automate pull request body summarization?▼

Yes, you need the GitHub CLI installed to automate pull request body summarization. This Skill requires both Git commands and the GitHub CLI for context retrieval and updating the PR title and description on your repository.

Why does my automated PR title generation fail when there are no new commits?▼

Automated PR title generation might seem to fail when there are no new commits, but this Skill handles that exact edge case. It processes uncommitted changes and untracked files to ensure a conventional commit-style title is still generated.