create-pull-request

Create a draft GitHub pull request with Jira ticket context.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jordanfbrown/dotfiles --skill create-pull-request-jordanfbrown
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pull-request
Source: https://github.com/jordanfbrown/dotfiles/tree/main/claude/dot-claude/skills/create-pull-request
Command: npx skills add https://github.com/jordanfbrown/dotfiles --skill create-pull-request-jordanfbrown

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates Jira-backed work into GitHub pull requests by auto-gathering ticket context and preparing a ready-to-review PR.

Core Features & Use Cases

  • Extract the Jira ticket ID from the current branch name (pattern [a-z]+-[0-9]+).
  • Fetch ticket details (summary, description, acceptance criteria, type) using jira CLI.
  • Analyze Git changes between BASE and HEAD to summarize what changed and why.
  • Find an existing PR template across common locations, or fall back to a default template.
  • Generate a PR content with a title in the form [TICKET-ID] Brief summary and a body that includes Jira context, changes, and a link to the Jira ticket.
  • Preview the generated PR and create a draft PR with gh pr create.

Quick Start

On a feature branch, run the tool to generate a draft PR linked to the Jira ticket.

Frequently Asked Questions about create-pull-request

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

FAQPage Schema
How do I create a GitHub pull request from a Jira ticket?

Creating a GitHub pull request from a Jira ticket involves parsing the branch name for the ticket ID, fetching Jira context, and generating a draft PR with a title and body summarizing the changes.

What is the best way to include Jira acceptance criteria in a GitHub PR?

The best way to include Jira acceptance criteria in a GitHub PR is to use an automation tool that fetches ticket details via jira CLI and populates the PR body with the summary and acceptance criteria.

Does creating a PR with jira CLI require a specific branch naming convention?

Yes, creating a PR with jira CLI requires your branch name to match the pattern [a-z]+-[0-9]+ so the tool can extract the Jira ticket ID and fetch the correct ticket context.

How to analyze Git diff and generate a PR summary automatically?

To analyze Git diff and generate a PR summary automatically, the tool compares changes between BASE and HEAD, discovers PR templates, and formats the diff analysis into the PR body.

Can I use gh pr create to link a Jira ticket to a draft pull request?

Yes, you can use gh pr create to link a Jira ticket to a draft pull request by extracting the ticket ID from the branch name and including a direct link to the Jira ticket in the PR body.

What happens if there is no pull request template in the repository?

If there is no pull request template in the repository, the automation falls back to a default template to ensure the PR body still includes the Jira context and diff summary.