create-pr

Creates GitHub pull requests by analyzing all branch commits with gh CLI.

17|1|Updated Dec 29, 2019
One-click install
npx skills add https://github.com/LumaKernel/dotfiles --skill create-pr-lumakernel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/LumaKernel/dotfiles/tree/main/common/claude/skills/create-pr
Command: npx skills add https://github.com/LumaKernel/dotfiles --skill create-pr-lumakernel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing pull request titles and descriptions manually is repetitive, and it is easy to overlook earlier commits when summarizing a branch. This Skill automates PR creation by analyzing every commit on the branch and generating a concise, consistently formatted pull request via the GitHub CLI. ## Core Features & Use Cases - Full-branch commit analysis: Reviews all commits and the complete diff from the base branch, not just the latest commit, to capture the true scope of changes. - Standardized PR format: Generates a title under 70 characters and a body following a fixed Summary template, deliberately omitting a Test Plan section. - End-to-end automation: Checks git status, pushes the branch to the remote if needed, creates the PR with gh pr create, and returns the PR URL. - Use Case: After finishing a feature branch with five commits, invoke the Skill to get a ready-to-review GitHub PR with an accurate summary and a shareable URL, without writing anything by hand. ## Quick Start Ask the assistant to create a pull request for the current branch using the create-pr skill.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I create a GitHub pull request from the command line?▼

Use the GitHub CLI command gh pr create after pushing your branch with git push -u origin HEAD. This Skill automates the full flow: checking git status, analyzing commits, pushing, and creating the PR with a formatted title and body.

How to write a good pull request title and description?▼

Keep the title under 70 characters and focused on the essence of the change. The body should contain a Summary section with one to three bullet points describing the purpose and content, based on all commits in the branch rather than only the latest one.

Why does gh pr view fail with GitHub Projects?▼

gh pr view is affected by the deprecation of GitHub Projects Classic and may not work reliably. This Skill avoids it entirely, using gh pr create and the gh api command for pull request operations instead.

What happens if my branch is not pushed to the remote?▼

The Skill checks whether the branch exists on the remote and runs git push -u origin HEAD if it does not. The pull request is only created after the branch is successfully pushed.

Does the generated pull request include a Test Plan section?▼

No. The PR body template intentionally excludes a Test Plan section and contains only a Summary section with bullet points. The body is passed via HEREDOC to prevent formatting issues.