create-pr

Create GitHub pull requests with template-informed titles and bodies.

8|Updated Jul 7, 2017
One-click install
npx skills add https://github.com/ebkn/dotfiles --skill create-pr-ebkn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/ebkn/dotfiles/tree/main/root/.claude/skills/create-pr
Command: npx skills add https://github.com/ebkn/dotfiles --skill create-pr-ebkn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates drafting and creating GitHub pull requests by gathering repository context, applying PR templates, and composing clear, Conventional Commits–style titles and bodies to reduce manual writing and mistakes.

Core Features & Use Cases

  • Context gathering: discovers the default branch, recent commits, diffs, and uncommitted changes to build an accurate PR description.
  • Uncommitted changes handling: prompts the user to commit, ignore, or abort when there are local modifications.
  • PR template detection and filling: reads repository PR templates, preserves headings and comments, detects template language, and fills sections accordingly.
  • Title and body composition: drafts a concise Conventional Commits title (under 72 characters) and a populated body (or a Summary / Changes / Concerns / References structure if no template).
  • Safe publish flow: shows the full title and body for confirmation and only pushes/creates the PR after explicit user approval.
  • Use Cases: preparing feature, bugfix, or documentation pull requests with consistent titles and comprehensive descriptions across teams.

Quick Start

Create a pull request for the current branch using the repository's PR template, draft a Conventional Commits title and a filled template body, then confirm before pushing and creating the PR.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automate creating a GitHub pull request from local commits?

To automate creating a GitHub pull request, this Skill gathers your local git commits, diffs, and repository context to draft a PR title and body. It then prompts for explicit user confirmation before pushing the branch and running the `gh pr create` command.

How does a PR template get filled out automatically?

PR template filling works by reading the repository's existing pull request template, detecting its language, and preserving headings and comments. The Skill populates the template sections using the context gathered from your recent commits and uncommitted changes.

Can I generate Conventional Commits titles for my pull requests?

Yes, you can generate Conventional Commits titles for pull requests. The Skill drafts a concise title strictly under 72 characters based on the context of your current branch's commits to ensure compliance with Conventional Commits standards.

Do I need the GitHub CLI installed to create context-aware pull requests?

Yes, you need the GitHub CLI (gh) installed and accessible to create context-aware pull requests. The Skill requires both git and the `gh` command-line tool to read repository files, push local commits, and execute the final PR creation.

What happens to uncommitted changes when preparing a pull request?

When preparing a pull request with uncommitted changes, the Skill pauses and prompts you to either commit, ignore, or abort the operation. This ensures your local modifications are intentionally handled before the branch is pushed.

What is the structure of a pull request body when no template exists?

When no PR template exists, the pull request body defaults to a structured format containing Summary, Changes, Concerns, and References sections. This structure organizes the gathered commit and diff context into a comprehensive description.