create-pr

Create a pull request for the current branch using the gh CLI.

Updated Aug 23, 2026

Search Tags:#automation #git #pr #pull-request #gh-cli #branch-name

Ready to run

npx skills add https://github.com/seanwachs/cursor-skills --skill create-pr-seanwachs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/seanwachs/cursor-skills/tree/main/.agents/skills/create-pr
Command: npx skills add https://github.com/seanwachs/cursor-skills --skill create-pr-seanwachs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically creates a pull request for the current branch using the gh CLI, reducing manual steps and ensuring consistent PR metadata.

Core Features & Use Cases

Extracts Jira ticket numbers from the branch name to anchor PR context
Builds PR title and body from diffs and commit history for clear reviews
Pushes the branch and opens the PR for review, integrating with standard workflows
Enriches the PR body with Jira issue context when available via MCP, or falls back to branch/commit history when not

Quick Start

Run this on a checked-out branch to create and open a PR with a descriptive title and body.

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 pull request from the command line?▼

You can automate creating a pull request using the gh CLI to extract Jira ticket numbers from the branch name and build a PR title and body from commit history and diffs.

How do I generate a PR title and description from git commit history?▼

Generating a PR title and description from git commit history is done by parsing branch diffs and extracting Jira ticket numbers to anchor the PR context for clear reviews.

Can I enrich a pull request body with Jira issue context automatically?▼

Yes, you can enrich a pull request body with Jira issue context automatically when the Jira MCP is available, falling back to branch name and commits for context when it is not.

What is the best way to create consistent PR metadata across multiple branches?▼

The best way to create consistent PR metadata is automating the process to extract Jira ticket numbers from branch names and build standardized titles and descriptions from diffs.

Does creating a PR automatically push my current branch to the remote repository?▼

Yes, creating a PR automatically pushes your current branch to the remote repository and opens the PR for review using the gh CLI as part of the standard workflow integration.