pr

Create a GitHub pull request for the current branch using gh.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/andershi666/lobehub-hr-demo --skill pr-andershi666
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/andershi666/lobehub-hr-demo/tree/main/lobehub/.agents/skills/pr
Command: npx skills add https://github.com/andershi666/lobehub-hr-demo --skill pr-andershi666

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of a pull request for the current branch, reducing manual steps and ensuring consistent PR workflows across repositories.

Core Features & Use Cases

  • Branch context gathering: current branch, status, upstream, and unpushed commits.
  • PR creation with gh pr create, including automatic base choice, title/body templating, and issue linking.
  • Branch management support: on-canary-or-main with uncommitted changes, create a new branch, commit, and continue.
  • Open PR in browser and reference existing PRs/issues as needed.

Quick Start

Ask the AI to create a pull request for the current branch using the canary base and the PR template.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I create a pull request for my current branch in one step?

To create a pull request, this automation gathers your current branch context, unpushed commits, and upstream status, then executes gh pr create with templated bodies and issue linking automatically.

Can I create a pull request from a canary or main branch with uncommitted changes?

Yes, when on a canary or main branch with uncommitted changes, it creates a new branch, commits your changes, and continues the pull request creation workflow seamlessly.

How does branch detection work when automating a pull request?

Branch detection analyzes your current branch status, upstream tracking, and unpushed commits to determine the appropriate base, ensuring the pull request targets the correct integration branch.

What is the best way to link issues when creating a GitHub pull request?

The best way to link issues is through automated templated PR bodies, which reference existing pull requests and issues during the gh pr create execution for your current branch.

Do I need the GitHub CLI installed to automate pull request creation?

Yes, automating pull request creation requires the GitHub CLI, as the workflow executes the gh pr create command to push changes, apply templates, and open the PR in your browser.

Why does my automated pull request workflow need diff analysis?

Diff analysis is needed to gather branch context and unpushed commits, allowing the pull request automation to generate accurate titles, populate templates, and link relevant issues automatically.