pr

Create or update GitHub Pull Requests from the current branch.

2|Updated Apr 6, 2017
One-click install
npx skills add https://github.com/shiiman/dotfiles --skill pr-shiiman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/shiiman/dotfiles/tree/main/.claude/skills/pr
Command: npx skills add https://github.com/shiiman/dotfiles --skill pr-shiiman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate creating or updating GitHub Pull Requests from your current branch, saving time and ensuring PRs reference related work.

Core Features & Use Cases

  • Create PRs from the active branch with an automatically inferred title.
  • Update an existing PR if a PR already exists for the branch.
  • Auto-detect related issues from the branch name and include references in the PR body.
  • Optionally specify base branch and draft status through prompts when needed.

Quick Start

Ask the AI to create or update a PR from your current branch, optionally providing a title and base.

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 from my current git branch automatically?

To create a pull request from your current git branch automatically, the Skill inspects your branch state and invokes GitHub CLI to generate PR metadata with an inferred title. It auto-detects related issues from the branch name and applies them to the PR body.

Can I update an existing GitHub pull request from the checked-out branch?

Yes, you can update an existing GitHub pull request from the checked-out branch. If a PR already exists for the active branch, the Skill invokes gh pr edit to update the metadata, modifying the computed title and body without creating a duplicate request.

Does creating a PR with GitHub CLI require uncommitted changes to be pushed first?

Creating a PR with GitHub CLI inspects the active branch for uncommitted or unpushed changes before proceeding. The Skill requires Git and gh CLI access to ensure your local branch state is synchronized with the remote repository prior to opening the pull request.

How does auto-detecting issues from a branch name work for pull requests?

Auto-detecting issues from a branch name works by parsing the active git branch name for issue references. The Skill uses this parsed data to automatically generate PR body metadata, linking the pull request to the relevant feature, bugfix, or topic issue.

What's the best way to set a draft status or base branch when creating a pull request?

The best way to set a draft status or base branch when creating a pull request is through optional prompts. The Skill triggers these prompts during the gh pr create workflow, allowing you to specify the target base branch and toggle draft status as needed.

Why does my pull request creation fail when using this branch automation?

Pull request creation automation fails if Git or GitHub CLI is not installed or authenticated. The Skill depends on gh pr create and gh pr edit commands, requiring proper CLI access and a clean, pushed branch state to compute and submit PR metadata successfully.