pr

Creates or updates GitHub pull requests for the current branch using gh CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Preparing a pull request involves many small, error-prone steps: checking branch state, detecting overlapping work, reviewing your own diff, writing a standards-compliant title and description, and linking related issues. This Skill automates that entire workflow so a PR is created or updated correctly every time. ## Core Features & Use Cases - End-to-end PR workflow: Gathers branch context, checks for overlapping open PRs, prepares and pushes the branch, then creates or updates the PR with gh pr create and gh pr edit. - Built-in self-review pass: Inspects the diff against the base branch before human review, sweeping for dead code, weak abstractions, and comment slop, and folds clear fixes into scoped commits. - Standards-compliant content: Delegates title, description, release note, and code-change table standards to the companion write-pr skill, and links related issues with Closes #123 syntax. - Use Case: You finished a feature branch and want it reviewed. Invoke the skill and it checks for a teammate's overlapping PR, reviews your diff, fixes minor issues, pushes the branch, and opens a properly formatted PR with linked issues. ## Quick Start Create a pull request for my current branch and link any related issues you find.

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 the command line?▼

Use the GitHub CLI with `gh pr create` after committing and pushing your branch. This skill automates the full flow: gathering branch context, pushing changes, creating the PR, and linking related issues with `Closes #123` syntax.

How do I update an existing pull request title or description?▼

Use `gh pr view --json title,labels,number` to read the current PR state, then `gh pr edit` to update the title or body. The skill compares the existing PR against the current diff and updates it when they no longer match.

Can this skill push or commit changes automatically?▼

It commits and pushes only changes within the user's explicitly requested scope, excluding secrets and private content. It never force pushes or force commits, and a content-only PR request does not authorize new code commits.

What happens if a teammate already has a PR for the same work?▼

The skill lists open PRs and compares changed files to detect real overlap. It prefers building on the existing PR through reviews or follow-up commits, and only opens a competing PR when approaches genuinely diverge, linking both for reviewers.

What are the limitations of this pull request workflow?▼

It requires the GitHub CLI and a GitHub-hosted repository, and it depends on the companion write-pr skill for content standards. Hook failures requiring product or design decisions stop the workflow and ask the user rather than guessing.