create-pr

Name: create-pr
Availability: InStock
Author: gtapps

Create a pull request from a feature branch with a drafted title and body.

69|12|Updated Mar 23, 2026

Search Tags:#automation #git #workflow #github #branch-management #pull-request

Ready to run

npx skills add https://github.com/gtapps/claude-code-hermit --skill create-pr-gtapps

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/gtapps/claude-code-hermit/tree/main/plugins/claude-code-dev-hermit/.claude/skills/create-pr
Command: npx skills add https://github.com/gtapps/claude-code-hermit --skill create-pr-gtapps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft PR creation from a feature branch by automatically composing a PR title and body from commits and diffs, then opening the PR via GitHub CLI, saving time and ensuring consistency.

Core Features & Use Cases

Guardrails: validate branch state (not on main/default), detect dirty working trees, and avoid creating PRs when none are ahead in the branch history.
Drafting & automation: generate a clean title and body from commits and diffs, push if needed, and open the PR with gh pr create.
Use cases: accelerate code review for feature branches and maintain a repeatable PR workflow across projects.

Quick Start

On a feature branch, say "open a PR" to start the PR creation workflow.

Frequently Asked Questions about create-pr

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

FAQPage Schema

How do I automatically generate a pull request title and body from git commits?▼

Yes, you can open a GitHub pull request from a feature branch using the gh pr create command. This skill automates that process by generating the title and body from your commits and diff, then publishing the PR for you.

How do I create a pull request with guardrails to prevent pushing to the main branch?▼

Creating a pull request with guardrails prevents accidental pushes to the main or default branch. This skill validates your current branch, checks for a dirty working tree, and ensures no existing open PR before proceeding with PR creation.

What happens if my working tree is dirty when I try to open a PR?▼

If your working tree is dirty when you try to open a PR, the skill's guardrails will halt the process to ensure a clean state. You must commit or stash changes before the automated PR creation workflow can proceed.

Can I use this automated PR workflow to force-push or merge branches?▼

No, you cannot use this automated PR workflow to force-push or merge branches. The skill explicitly forbids destructive actions like force-pushes and merges, focusing solely on safely opening pull requests from feature branches.

Does this PR automation tool check for existing open pull requests before creating a new one?▼

Yes, this PR automation tool checks for existing open pull requests before creating a new one. Its guardrails ensure you do not duplicate an open PR for the same branch, maintaining a clean and repeatable workflow.

What is the best way to accelerate code review for feature branches?▼

The best way to accelerate code review for feature branches is to automate PR drafting from commits and diffs. This skill generates consistent PR titles and bodies and opens them via GitHub CLI, saving time and ensuring repeatable workflows.