create-pr

Create pull requests from JIRA feature branches with template-based bodies.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of Pull Requests from JIRA ticket branches, streamlining the code review process.

Core Features & Use Cases

  • Automatic Parent Branch Detection: Intelligently identifies the base branch for your PR.
  • JIRA Link Insertion: Automatically includes a link to the relevant JIRA ticket.
  • Template-Based PR Body: Generates a structured PR description based on a template.
  • Use Case: When you finish a feature on a branch like PROJ-123-new-login-flow, simply run /create-pr and the skill will handle the rest, creating a PR targeting main or develop with a relevant title and description.

Quick Start

Run the create-pr skill with the command /create-pr.

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 JIRA ticket branches?

You can automate pull request creation from JIRA ticket branches by using a tool that detects the parent branch, inserts JIRA links, and generates a PR body from a predefined template.

Does this PR automation tool automatically detect the parent branch for merges?

Yes, PR automation tools can intelligently detect the parent branch, automatically identifying the correct base branch like main or develop for your code merges.

Can I automatically insert JIRA links into my GitHub pull request body?

Yes, you can automatically insert JIRA links into a GitHub pull request body by running an automation script that parses the feature branch name and appends the relevant ticket URL.

What is the best way to generate a structured pull request description from a template?

The best way to generate a structured pull request description is using template-based automation that formats the PR body automatically, streamlining the code review process.

Do I need a specific branch naming convention to link pull requests to JIRA tickets?

Yes, you typically need a branch naming convention that includes the JIRA ticket ID, such as PROJ-123-feature-name, so the automation can parse it and link the pull request correctly.