pr

Open a GitHub pull request linked to an issue from a branch name.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/ryan-mahoney/ryan-llm-skills --skill pr-ryan-mahoney
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/ryan-mahoney/ryan-llm-skills/tree/main/skills/pr
Command: npx skills add https://github.com/ryan-mahoney/ryan-llm-skills --skill pr-ryan-mahoney

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the process of opening a GitHub pull request by deriving the associated issue from the branch name or a provided argument, then preparing and submitting the PR.

Core Features & Use Cases

  • Issue-detection: Determine the issue number from the current branch name or explicit argument.
  • Commit & Push: Commit staged changes with a conventional message and push the branch to origin.
  • PR Creation: Open a PR with a concise, imperative title and a descriptive body that links to the issue.
  • Use Case: When a developer finishes work on a feature linked to an issue, run this skill to automatically prepare a PR referencing that issue.

Quick Start

Commit the staged changes, push the branch, and open a pull request referencing the identified GitHub issue.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I automatically open a pull request linked to a GitHub issue from my current branch?

To open a pull request linked to a GitHub issue, this skill derives the issue number from your current branch name or an explicit argument, commits staged changes, pushes to origin, and creates the PR with a linked issue reference.

Can I create a GitHub pull request from a branch name that contains an issue number?

Yes, you can create a GitHub pull request from a branch name containing an issue number. The skill auto-detects the issue number from the branch naming convention and uses it to link the pull request to that specific issue.

What's the best way to commit staged changes and push a branch to open a PR referencing an issue?

The best way to commit staged changes and open a PR is using this skill to apply a conventional commit message, push the branch to origin, and generate a concise imperative PR title with a descriptive body linked to the GitHub issue.

Do I need the GitHub CLI to automate pull request creation and issue detection?

Yes, you need the GitHub CLI to automate pull request creation. The skill reads issue context using the gh issue view command and uses the GitHub CLI to open the pull request once the branch is pushed to origin.

How does issue number detection work when preparing a pull request?

Issue number detection works by parsing the current branch name or accepting an explicit argument. Once the issue number is derived, the skill reads the issue context with gh issue view to prepare a descriptive PR body linking to it.

What happens if my branch name does not contain an issue number?

If your branch name does not contain an issue number, you can provide an explicit argument to locate the issue. The skill accepts this argument to derive the correct GitHub issue and link it to the pull request.