open-pr

Create a GitHub pull request from a feature branch with a template-based body.

Updated May 4, 2026
One-click install
npx skills add https://github.com/mhert/claude-code-helpers --skill open-pr-mhert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: open-pr
Source: https://github.com/mhert/claude-code-helpers/tree/main/skills/open-pr
Command: npx skills add https://github.com/mhert/claude-code-helpers --skill open-pr-mhert

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, acli, marklassian, and includes assets (resource) components.

What problem does it solve?

This Skill helps you reliably turn a local feature-branch change into a GitHub pull request with a consistent, reviewer-friendly body, including a confirmed ticket reference and a correctly scoped PR type.

Core Features & Use Cases

  • Ticket-confirmed PRs: Detects a Jira/Linear-style key from the branch or commit content, then requires user confirmation before proceeding.
  • Template-driven PR body: Uses a repo PR template when available, otherwise selects a type-specific fallback (bugfix/feature/misc) shipped with the Skill.
  • Safe GitHub workflow: Validates that you’re not on the default branch, ensures there’s something to push, pushes via a regular (non-force) push, and creates or edits the PR using gh.

Quick Start

Run the open-pr skill after you have committed your change to a feature branch and confirmed the ticket key when prompted.

Frequently Asked Questions about open-pr

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

FAQPage Schema
How do I create a GitHub pull request with a conventional commit type and linked ticket?

To create a GitHub pull request with a linked ticket, this Skill detects a Jira or Linear-style ticket key from your branch or commits and requires confirmation before opening a template-based PR using the gh CLI.

How does PR type derivation from conventional commits work when opening a GitHub PR?

PR type derivation from conventional commits works by reading local commit message prefixes on your feature branch, then selecting a matching type-specific fallback PR template like bugfix or feature if a repo template is unavailable.

What's the best way to prevent pushing uncommitted changes to a GitHub feature branch?

The best way to prevent pushing uncommitted changes is using built-in guardrails that block PR creation when uncommitted changes exist, ensuring only committed local branch state is published via a regular non-force push.

Does this PR workflow block execution if I'm still on the default branch?

Yes, this PR workflow blocks execution if you are on the default branch, enforcing safe GitHub workflows by validating branch context and ensuring there is something to push before creating or editing the PR.

Can I use my repository's PR template when creating a pull request with gh CLI?

Yes, you can use your repository's PR template when creating a pull request, as the workflow checks for an available repo PR template and falls back to type-specific templates shipped with the Skill if none is found.

Do I need to install jq and acli to open a GitHub PR with ticket linkage?

Yes, you need jq and acli installed, along with the gh CLI and marklassian, to handle ticket key detection, template processing, and automated PR creation or editing from your local feature branch.