pr

Opens a pre-populated GitHub PR creation page with a drafted title and body.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Drafting a good pull request title and body takes time, and creating a PR via CLI without review risks publishing an unedited draft. This Skill analyzes your branch's diff, writes a PR title and body in a consistent personal style, and opens a pre-filled GitHub PR page in the browser so you review and submit it yourself. ## Core Features & Use Cases - Diff-driven drafting: Reads commit subjects and diffs against the correct base branch (including stacked branches) to write an accurate title and body. - Style-matched writing: Follows a detailed personal PR style guide — no boilerplate "Test plan" sections, no file counts, no AI trailers, with patterns like Before/After diffs, callouts, and reviewer guidance. - Safe browser handoff: Uses gh pr create --web with a temp body file so nothing is created until you click submit in the browser. - Use Case: You finish a feature branch stacked on another branch, run the skill, and get a pre-filled GitHub PR page with the correct base branch and a body written in your voice — you just review and submit. ## Quick Start Ask the assistant to open a PR for the current branch, and it will draft the title and body from the diff and open the pre-filled GitHub page in your browser.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I open a pre-filled GitHub PR page without creating the PR?▼

Run gh pr create with the --web flag, which opens a pre-populated "Open a pull request" page in the browser without creating anything. Omitting --web creates the PR instantly with no chance to edit, so the flag is mandatory.

How do I create a PR for a stacked branch with the correct base?▼

Find the nearest local branch ancestor using git log --oneline --graph --all or git merge-base, then pass it as --base to gh pr create. This ensures a branch stacked on another feature branch targets that branch instead of main.

Why does gh pr create --web fail with a URL length error?▼

The GitHub CLI refuses to open the browser when the full URL reaches 8192 bytes, erroring with "cannot open in browser: maximum URL length exceeded". This corresponds to roughly an 8 KB PR body, so shorten the body rather than dropping content silently.

Can I pass a multi-line PR body to gh pr create from the command line?▼

Pass the body via --body-file pointing to a temp file created with mktemp rather than inline. Bodies containing backticks, dollar signs, quotes, and newlines get mangled by shell expansion when passed inline.

Does this skill create the pull request automatically?▼

No, it only opens the pre-filled PR creation page in the browser using gh pr create --web. The user reviews the drafted title and body, edits if needed, and submits the PR manually.