create-pr

Create pull requests with GitHub CLI using a standardized template and Jira ticket extraction.

1|Updated Feb 11, 2019
One-click install
npx skills add https://github.com/ddieppa/dotfiles --skill create-pr-ddieppa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/ddieppa/dotfiles/tree/main/.agents/skills/create-pr
Command: npx skills add https://github.com/ddieppa/dotfiles --skill create-pr-ddieppa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve?

Generating pull requests often leads to inconsistent descriptions and missed ticket references. This Skill automates PR creation using gh CLI with a standardized template and Jira ticket extraction from branch names, ensuring consistent PR bodies and titles.

Core Features & Use Cases

  • Standardized PR templates via assets/pr-template.md to enforce consistency across PRs.
  • Branch parsing to extract Jira tickets (MCA-XXX, PERF-XXX) from branch names and include them in the PR title and body.
  • Pre-checks and guidance via scripts/check-pr-ready.ps1 to verify clean working directory and readiness before PR creation.
  • Clear examples and workflow guidance for end-to-end PR creation in typical software development scenarios.

Quick Start

Create a PR from your current branch using gh to apply the standardized template and automatically extract the Jira ticket from the branch name.

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 with a standardized template using GitHub CLI?

Automate pull request creation by using the GitHub CLI with a standardized PR template to enforce consistency. The Skill extracts Jira tickets from branch names and applies a template to compose well-structured PR titles and bodies automatically.

Can I extract Jira ticket IDs from branch names when creating a PR?

Yes, you can extract Jira ticket IDs from branch names during PR creation. The Skill parses branch names for specific ticket formats like MCA-XXX and PERF-XXX, then automatically includes those references in the generated PR title and body.

What's the best way to ensure consistent PR descriptions across a development team?

To ensure consistent PR descriptions, use a standardized markdown PR template applied through GitHub CLI automation. This enforces uniform structure across all pull requests while automatically injecting relevant Jira ticket references extracted from branch names.

Do I need GitHub CLI to be authenticated before creating pull requests with templates?

Yes, GitHub CLI must be authenticated and available before creating pull requests with templates. The Skill relies on the gh CLI to publish PRs and uses a pre-check script to verify working directory cleanliness and overall readiness before submission.

How does branch parsing work when generating a pull request title and body?

Branch parsing extracts Jira ticket identifiers from the current branch name using pattern matching for formats like MCA-XXX and PERF-XXX. These extracted tickets are then automatically embedded into the standardized PR title and body generated from the template.

What pre-checks are performed to verify readiness before publishing a pull request?

Pre-checks verify working directory cleanliness and overall PR readiness before publishing. A dedicated PowerShell script validates the environment state to ensure the branch is ready for pull request creation via the authenticated GitHub CLI.