gh-pr

Create, update, and comment on GitHub pull requests with PR body generation.

10|4|Updated Nov 12, 2025
One-click install
npx skills add https://github.com/technicalpickles/pickled-claude-plugins --skill gh-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-pr
Source: https://github.com/technicalpickles/pickled-claude-plugins/tree/main/plugins/git-workflows/skills/gh-pr
Command: npx skills add https://github.com/technicalpickles/pickled-claude-plugins --skill gh-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating and managing GitHub Pull Requests (PRs) can be time-consuming, often leading to verbose descriptions, accidental commits of temporary files, or inefficient communication with reviewers. This skill automates PR workflows while ensuring clarity, safety, and reviewer respect.

Core Features & Use Cases

  • Safe PR Creation & Updates: Drafts PR bodies to a .scratch/pr-bodies/ area first, preventing accidental commits, and detects manual edits before overwriting.
  • Material Impact Communication: Focuses PR descriptions on "why it matters" and "what problem it solves," avoiding unnecessary metrics or implementation details visible in the diff.
  • Smart Workflow Routing: Intelligently decides whether to update a PR body or add a comment based on review activity, ensuring appropriate communication and notifications.

Quick Start

"Create a pull request for my current branch."

Frequently Asked Questions about gh-pr

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

FAQPage Schema
How do I automate creating GitHub pull requests from the command line?

Automate GitHub PR creation by drafting PR bodies to a safe `.scratch/pr-bodies/` directory first, then pushing to GitHub. This Skill handles body generation, branch metadata, and reviewer communication for feature branches, preventing accidental commits of temporary files while keeping descriptions focused on material impact.

Can I safely update PR descriptions without overwriting manual edits?

Yes. This Skill detects manual edits to existing PR bodies before applying updates, using a hash of the last generated version. It routes updates as PR comments when review activity is detected, preserving reviewer context and avoiding notification fatigue.

How do I write PR descriptions that focus on why changes matter, not implementation details?

PR descriptions should emphasize the problem solved and material impact rather than implementation details visible in diffs. This Skill generates human-friendly PR bodies emphasizing why changes matter, then manages updates and comments intelligently across multiple PRs as reviews progress.

What's the best way to communicate with reviewers across multiple pull requests?

Route communications through PR comments when ongoing reviews are detected, preserving context and avoiding redundant notifications. This Skill intelligently decides whether to update PR body or add comments based on review activity, with explicit operation routing and comprehensive PR metadata handling.

Does this work with feature-branch workflows?

Yes. This Skill is applicable to feature-branch PRs and ongoing reviews, tracking branch, base, title, creation time, and last-updated timestamps. It handles material-impact communication and smart merge behavior across the entire PR lifecycle.

Why should I draft PR bodies separately before committing to GitHub?

Drafting PR bodies to `.scratch/pr-bodies/` first prevents accidental commits of temporary files and ensures PR descriptions remain focused on material impact. You review and refine before GitHub submission, maintaining clarity and preventing verbose or unfocused descriptions.