create-pr

Automate GitHub PR creation with Jira IDs and conventional commit formatting.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/ketronkowski/skills --skill create-pr-ketronkowski
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/ketronkowski/skills/tree/main/create-pr
Command: npx skills add https://github.com/ketronkowski/skills --skill create-pr-ketronkowski

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of GitHub Pull Requests by enforcing team conventions and integrating with Jira, reducing manual formatting toil and speeding up development workflows.

Core Features & Use Cases

  • PR status validation: ensures updates are limited to open PRs and creates new PRs when previous ones are merged or closed.
  • Jira work item discovery: discovers relevant Jira items to attach to the PR title and description.
  • Title/description formatting: applies Jira ID or conventional commit formats for consistent PR metadata across repositories.

Quick Start

Use the create-pr skill to open a PR by providing a target branch, a Jira ID, or a conventional-commit style title. For example: GLCP-313119: Add deployment configuration or feat: add new API endpoint.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automate GitHub PR creation with Jira IDs?

You can automate GitHub PR creation with Jira IDs by using a skill that discovers relevant Jira work items and applies standardized title and description formatting, reducing manual toil.

How does PR status validation work for automated pull requests?

PR status validation ensures updates are limited to open PRs and automatically creates new PRs when previous ones are merged or closed, maintaining a clean workflow.

Can I use conventional commit formats for GitHub pull request titles?

Yes, you can use conventional commit formats for GitHub pull request titles by providing a conventional-commit style title like feat: add new API endpoint to apply consistent PR metadata.

What is the best way to link a Jira work item to a GitHub pull request?

The best way to link a Jira work item to a GitHub pull request is through guided prompts that discover the Jira ID and attach it to the PR title and description automatically.

Do I need a specific Jira ID format to open a GitHub pull request?

You need a valid Jira ID or a conventional-commit style title to open a GitHub pull request, which the skill uses to apply templated formatting and enforce team conventions.