skills.rest
flurdy
flurdyCOMMUNITY
Explore all skills by this author →
Website𝕏@flurdyGitHub

create-pr

Create pull requests from feature branches using Jira ticket parsing.

6|Updated Jan 22, 2026
Search Tags:#automation#git#jira#pr#code-review#pull-request#branch-name
One-click install
npx skills add https://github.com/flurdy/agent-skills --skill create-pr-flurdy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/flurdy/agent-skills/tree/main/skills/create-pr
Command: npx skills add https://github.com/flurdy/agent-skills --skill create-pr-flurdy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of pull requests from the current branch, ensuring consistency with project conventions and Jira ticket integration.

Core Features & Use Cases

  • Parse branch names to identify Jira tickets and derive PR scope.
  • Retrieve ticket details to craft meaningful PR descriptions.
  • Generate PR titles using conventional commit formats based on branch prefixes.
  • Produce PR bodies from code changes and optional templates, then push the branch and create the PR.
  • Handle end-to-end PR creation in standard workflows for Claude/Codex-like agents.

Quick Start

Create a PR by invoking the /create-pr command to start the automated workflow.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automate pull request creation from a Jira feature branch?▼

Automating pull request creation from a Jira feature branch involves parsing the branch name to extract the Jira ticket, retrieving ticket details, and generating a conventional commit PR title and description before pushing the branch.

Can I generate conventional commit PR titles from my git branch name?▼

Yes, you can generate conventional commit PR titles by parsing branch naming prefixes and deriving the PR scope. This workflow uses the branch name structure to automatically construct a standardized PR title.

How do I populate a PR description using Jira ticket details and code changes?▼

To populate a PR description, the workflow retrieves Jira ticket details and combines them with code changes and optional PR templates. This builds a meaningful PR body that provides context directly from the Jira ticket.

Do I need Jira MCP tools and GitHub CLI to automate end-to-end PR creation?▼

Yes, automating end-to-end PR creation requires Jira or Jira MCP tools for ticket lookup, GitHub CLI for pushing the branch, and standard PR templates. Branch naming conventions are also required to parse ticket information correctly.

What is the best way to ensure PR consistency with Jira integration and conventional commit standards?▼

The best way to ensure PR consistency with Jira integration and conventional commit standards is to automate ticket lookup, PR title generation, and description construction directly from the feature branch name using git and automation tooling.

Why does my automated PR workflow require specific branch naming conventions?▼

Automated PR workflows require specific branch naming conventions because the system parses the branch name to identify the associated Jira ticket. Without a standardized branch name, the tool cannot accurately look up the ticket or derive the PR scope.

Related Skills

Explore More Software Engineering Skills→
jjmartresjjmartres
40

work-on-ticket

Fetch Jira ticket details, create a named branch, and start task planning.

Community
Advanced
adobecomadobecom
1

sync-pr-jira

Automates synchronization of GitHub pull request statuses with Jira ticket statuses.

Official
Intermediate
vanman2024vanman2024
3

Git Workflows

Standardize git workflows with commit templates, branch helpers, and hook scripts.

Community
Basic
FutureAtomsFutureAtoms
1

git-github-create-pr

Generates GitHub pull requests with titles, descriptions, reviewers, and labels.

Community
Advanced