pr

Create, update, and review GitHub PRs using structured templates and CLI commands.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Creating, updating, and reviewing GitHub pull requests is often inconsistent and tedious. This skill provides a structured workflow to generate well-formed PR descriptions using a standardized What/Why/How/Changes template and automated content population.

Core Features & Use Cases

  • Structured PR templates with What/Why/How/Changes sections to guide descriptions
  • Smart generation from commits and diffs to auto-fill PR content
  • Update existing PRs after new commits while preserving user edits
  • Review PRs with structured analysis and clear recommendations
  • Draft PRs support to facilitate work-in-progress submissions

Quick Start

Run the /pr create command to generate a structured PR from your current branch.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I automate GitHub pull request creation from git commits and diffs?

You can automate pull request creation by running a command that reads git history and diffs to populate structured What/Why/How/Changes sections in the PR description. This ensures consistent formatting and traceability without manual data entry.

What is a structured PR template and why use it for code review workflows?

A structured PR template enforces What/Why/How/Changes sections to guide descriptions and standardize code review workflows. It improves PR quality, traceability, and reviewer guidance across software development teams by maintaining consistent formatting.

Do I need gh CLI authentication to create and update GitHub PRs?

Yes, gh CLI authentication is required to automate the creation, updating, and reviewing of GitHub PRs. The workflow accesses git history and diffs through the CLI to populate structured PR templates with commit data.

Can I update an existing PR description after pushing new commits without losing edits?

Yes, you can update existing PRs after new commits while preserving user edits. The workflow reads updated git diffs and history to refresh the What/Why/How/Changes sections without overwriting your manual modifications.

How do I review a GitHub pull request with structured analysis and recommendations?

You can perform a structured PR review that analyzes the git diff and history to provide clear recommendations. The review process uses the same What/Why/How/Changes framework to ensure comprehensive evaluation and actionable feedback for code improvements.

Does the GitHub PR workflow support draft pull requests for work-in-progress branches?

Yes, the PR workflow supports draft PRs to facilitate work-in-progress submissions. You can create draft pull requests using the structured template generation, allowing reviewers to see early code changes before the final review.