github-pr

Automate GitHub pull request operations with gh CLI and jq.

8|2|Updated Jul 13, 2015

Search Tags:#automation #github #pr #code-review #pull-request #checks #gh-cli

Ready to run

npx skills add https://github.com/tstapler/dotfiles --skill github-pr-tstapler

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-pr
Source: https://github.com/tstapler/dotfiles/tree/main/.claude/skills/github-pr
Command: npx skills add https://github.com/tstapler/dotfiles --skill github-pr-tstapler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) and references (resource) components.

What problem does it solve?

GitHub PR workflows often require juggling multiple commands and contexts; this skill consolidates PR operations into a consistent, token-efficient pattern with structured outputs.

Core Features & Use Cases

View and summarize PR details with gh pr view and gh pr list using targeted fields, reducing context load.
Create PRs, manage reviews, request changes, and track merge readiness across repositories.
Inspect CI statuses and failing checks, and analyze review threads and comments to surface issues quickly.
Use REST and GraphQL patterns to fetch granular data (files changed, reviews, comments) without pulling full PR payloads.

Quick Start

Ask it to summarize a PR by printing its title, state, author, and latest reviews.

Frequently Asked Questions about github-pr

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

FAQPage Schema

How do I summarize a GitHub pull request without pulling the full payload?▼

You can summarize a GitHub pull request by using targeted fields with gh pr view and gh pr list. This approach fetches granular data like title, state, and author to reduce context load without pulling full payloads.

What's the best way to automate GitHub PR reviews and track merge readiness?▼

Automating GitHub PR reviews involves consolidating operations into a consistent pattern using gh CLI. You can manage reviews, request changes, inspect CI statuses, and analyze comment threads to track merge readiness efficiently across repositories.

Do I need jq and gh CLI to automate pull request status checks?▼

Yes, you need both gh CLI and jq to automate pull request status checks. The gh CLI interacts with GitHub repositories while jq formats the JSON outputs, enabling token-efficient queries and structured data extraction for failing checks.

Can I analyze review threads and comments across forks using GitHub CLI?▼

Yes, you can analyze review threads and comments across forks using GitHub CLI. It applies REST and GraphQL patterns to fetch granular data, buffers large outputs to /tmp as needed, and surfaces issues quickly without retrieving full PR payloads.

How do I create a pull request with structured outputs using gh?▼

You create a pull request with structured outputs by using targeted fields via --json and --jq flags in gh CLI. This method ensures token-efficient queries and consistent formatting across repos and forks.