pr

Creates or refreshes draft GitHub pull requests from committed branch work using gh CLI.

Updated Nov 17, 2025
One-click install
npx skills add https://github.com/vzakharov/vovazakharov.com --skill pr-vzakharov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/vzakharov/vovazakharov.com/tree/main/.claude/skills/pr
Command: npx skills add https://github.com/vzakharov/vovazakharov.com --skill pr-vzakharov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It removes the manual work of renaming auto-generated branches, pushing commits, and composing consistent PR titles, summaries, and QA checklists every time work is ready for review. ## Core Features & Use Cases - Branch rename and push: Detects harness auto-branch names like claude/<adjective>-<noun>-<hash> and renames them to semantic slugs before pushing. - Three operating modes: plan-open (body composed from a plan), fresh open from existing commits, and refresh that recomposes the body against the real diff via REST PATCH. - Structured PR body: Generates a conventional-commit title, a Summary section, a QA Checklist delegated to the qa-checklist skill, and an optional Closes #N line, then posts a squash-message proposal comment. - Use Case: After committing a feature on a branch, invoke "/pr" to push the branch, open a draft PR against main with a composed title and body, and have the squash proposal posted as a comment automatically. ## Quick Start Say "/pr" or "open a draft PR" after committing your work to push the branch and create or refresh the draft pull request.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I open a draft pull request from the command line?

Use gh pr create with the --draft flag, a --base branch, and a --title and --body composed from your commits. This skill automates that flow: it pushes the branch, composes the title and body from the commit log and diff, and opens the draft PR.

How do I update an existing pull request body without gh pr edit?

Use the GitHub REST API with a PATCH request to repos/<owner>/<repo>/pulls/<PR> instead of gh pr edit. This avoids the projectCards query failure that gh pr edit hits where classic projects are deprecated, and avoids re-asserting the base branch.

What happens if a pull request already exists for my branch?

The skill switches to refresh mode instead of failing. It reads the existing PR's baseRefName as the base, recomposes the body against the real diff, and PATCHes the title and body over REST rather than creating a duplicate PR.

Why does gh pr create fail with no known GitHub host error?

In remote execution environments a proxy quirk makes gh unable to map git remotes to a GitHub host. Re-run the command with --repo OWNER/REPO explicitly, resolving the value from git remote get-url origin.

When should I not run this PR creation workflow?

Do not run it with uncommitted changes, with zero commits ahead of the base branch, or when you intend to mark a PR ready for review or run CI. Those belong to a separate finalize step; this skill only opens or refreshes the draft.