pr-generator

Generate conventional commit-formatted pull request titles and descriptions from git branch differences.

1|Updated Jan 19, 2026

Search Tags:#automation #git #code review #pull request #conventional commits #github

Ready to run

npx skills add https://github.com/jarrett-au/cc-config-starter --skill pr-generator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-generator
Source: https://github.com/jarrett-au/cc-config-starter/tree/main/skills/pr-generator
Command: npx skills add https://github.com/jarrett-au/cc-config-starter --skill pr-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the creation of well-formatted Pull Request titles and descriptions by analyzing your git branch changes, saving you time and ensuring consistency.

Core Features & Use Cases

Automated Title Generation: Creates conventional commit-formatted titles based on commit messages and file changes.
Description Summarization: Generates concise summaries of changes and lists modified files.
Use Case: After completing a feature on a new branch, use this Skill to draft a PR title like feat(auth): implement user login and a description detailing the changes made, ready for review.

Quick Start

Use the pr-generator skill to create a pull request title and description for the current branch.

Frequently Asked Questions about pr-generator

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

FAQPage Schema

How do I automatically generate a pull request title from git branch changes?▼

Automatically generating a pull request title from git branch changes involves analyzing commit messages and file diffs to produce conventional commit-formatted titles like 'feat(auth): implement user login', ensuring consistent PR naming across software development workflows.

What is conventional commit formatting for pull request descriptions?▼

Conventional commit formatting for pull requests uses structured prefixes like 'feat' or 'fix' followed by a colon and description, systematically summarizing code changes to document features and facilitate code reviews.

Can I use gh CLI commands to gather commit messages and file diffs for PR creation?▼

Yes, you can use gh CLI commands alongside git to gather commit messages, file diffs, and existing PR data for intelligent analysis, populating detailed pull request descriptions and titles automatically.

How do I summarize code changes for a pull request description?▼

To summarize code changes for a pull request description, analyze git branch differences to extract concise summaries of modifications and list modified files, detailing changes made for code review.

Do I need a GitHub remote to generate pull request titles and descriptions?▼

Generating pull request titles and descriptions primarily requires local git branch differences, but leveraging gh CLI commands to gather existing PR data requires a GitHub remote, while git diff analysis works independently.

What's the best way to draft PR titles for code review from git diffs?▼

The best way to draft PR titles for code review from git diffs is to apply conventional commit formats based on commit messages and file changes, automating well-formatted, review-ready titles.