gh-pr

Create GitHub pull requests with standardized bodies and current-user assignment.

253|7|Updated Apr 8, 2016
One-click install
npx skills add https://github.com/fredrikaverpil/dotfiles --skill gh-pr-fredrikaverpil
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-pr
Source: https://github.com/fredrikaverpil/dotfiles/tree/main/stow/shared/.claude/skills/gh-pr
Command: npx skills add https://github.com/fredrikaverpil/dotfiles --skill gh-pr-fredrikaverpil

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures GitHub pull requests follow a consistent structure and are assigned to the right people, reducing review friction.

Core Features & Use Cases

  • PR Body Template: Why/What/Notes sections to capture rationale and changes
  • Automation: Command wrapper for gh pr create with sensible defaults
  • Consistency: Enforces preferred assignment and formatting

Quick Start

Example: gh pr create --assignee @me --title "Add feature" --body "Why?

What?

Notes "

Frequently Asked Questions about gh-pr

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

FAQPage Schema
How do I automate GitHub pull request creation with consistent formatting?

Automate PR creation by wrapping the gh CLI with a template that enforces standardized structure: Why?/What?/Notes sections, concise titles, and automatic assignment to the current user, reducing review friction across repositories.

What structure should a GitHub pull request body follow?

A well-structured PR body captures rationale, changes, and optional notes through three sections: Why? explains motivation, What? describes the changes made, and Notes provides additional context or caveats.

Can I enforce consistent PR assignment and formatting across my team?

Yes, by using a gh CLI wrapper that applies sensible defaults—standardized body templates, imperative-style titles, and automatic assignment—you ensure every PR follows your team's preferred structure without manual effort.

How do I create a GitHub PR with the gh command-line tool?

Use gh pr create with flags for title, body, and assignee; a PR template enforces the Why?/What?/Notes format and automatically assigns to the current user, streamlining the creation workflow.

What's the best way to standardize pull request practices across repositories?

Implement a consistent PR body template that includes sections for motivation and changes, paired with automated assignment; this reduces friction during code review and ensures clear communication across all repositories.