create-pr

Create GitHub pull requests with auto-generated titles and descriptions from branch commits.

1|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/guicaulada/dotfiles --skill create-pr-guicaulada
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/guicaulada/dotfiles/tree/main/home/dot_claude/exact_skills/create-pr
Command: npx skills add https://github.com/guicaulada/dotfiles --skill create-pr-guicaulada

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces the friction of creating pull requests by automatically analyzing branch commits, discovering related issues and PRs, and producing a concise, conventional PR title and a contextual PR body so humans can review and submit quickly.

Core Features & Use Cases

  • Commit and diff analysis: Collects commits and full diff relative to the default branch to summarize changes.
  • Issue and PR discovery: Extracts referenced issue numbers from commits and the branch name and finds related open or merged PRs for context.
  • Safe creation flow: Validates branch state, checks for uncommitted changes, optionally pushes the branch, and opens the PR in the browser for human review.
  • Use Case: When working on a feature branch with multiple commits and referenced issues, use this Skill to generate a conventional, <=72-character title and a minimal, informative description that closes or links issues.

Quick Start

Create a pull request for the current branch by analyzing commits, discovering related issues, generating a title and body, and opening the PR in your browser for review.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I generate a pull request title and description automatically from git commits?

Automatically generate a pull request title and description by analyzing branch commits and extracting the full diff relative to the default branch. This process summarizes code changes to produce a concise, conventional title and an informative PR body.

How do I link related GitHub issues to a pull request automatically?

Link related GitHub issues automatically by discovering referenced issue numbers extracted from commit messages and the branch name. The generated pull request body includes these links to close or reference the relevant issues directly.

Can I use gh-cli to create a pull request and open it in the browser for review?

Yes, you can create a pull request and open it in the browser for human review using gh-cli. The workflow validates the branch state, optionally pushes the branch, and opens the finalized PR directly in your browser.

Do I need git and GitHub CLI to auto-generate pull requests from branch analysis?

Yes, git and GitHub CLI (gh) access are required to auto-generate pull requests. Git provides branch and diff analysis for summarizing commits, while gh-cli handles push checks and opening the PR in the browser for review.

What is the best way to write a conventional commit pull request title for multiple commits?

The best way to write a conventional PR title for multiple commits is by analyzing the collective branch diff against the default branch. This ensures the auto-generated title accurately summarizes all changes and stays within 72 characters.

Why does my pull request creation workflow need to check for uncommitted changes?

Your pull request creation workflow checks for uncommitted changes to ensure branch state validation before generating the PR. This safe creation flow prevents incomplete work from being pushed and included in the final pull request diff analysis.