mcpbeat

Github Pr Query

github/github-pr-query

Query GitHub pull requests with jq filtering and reusable selectors.

2k tokens
context cost
the whole folder, loaded on every use
2
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
4864
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/github/gh-aw --skill github-pr-query

What comes with it

5 289 bytes besides the instruction
query-prs.sh

The instruction itself

11 sections, as written by the author

GitHub Pull Request Query Skill

Query GitHub pull requests efficiently with built-in jq filtering.

Important: jq Parameter is Optional

The --jq parameter is optional. Without --jq, this skill returns schema and data size information instead of full data.

Use this to avoid oversized responses and inspect structure before targeted queries.

Use --jq '.' to get all data, or use a more specific filter for targeted results.

Usage

Use this skill to query pull requests from the current repository or any specified repository.

Basic Query (Returns Schema Only)

To list pull requests from the current repository:

./query-prs.sh
# Returns schema and data size, not full data

Get All Data

To get all PR data:

./query-prs.sh --jq '.'

With Repository

To query a specific repository:

./query-prs.sh --repo owner/repo

With jq Filtering

Use the --jq argument to filter and transform the output:

# Get only open PRs
./query-prs.sh --jq '.[] | select(.state == "open")'

# Get PR numbers and titles
./query-prs.sh --jq '.[] | {number, title}'

# Get PRs by a specific author
./query-prs.sh --jq '.[] | select(.author.login == "username")'

# Get merged PRs from last week
./query-prs.sh --jq '.[] | select(.mergedAt != null)'

# Count PRs by state
./query-prs.sh --jq 'group_by(.state) | map({state: .[0].state, count: length})'

Common Options

  • --state: Filter by state (open, closed, merged, all). Default: open
  • --limit: Maximum number of PRs to fetch. Default: 30
  • --repo: Repository in owner/repo format. Default: current repo
  • --author: Filter PRs by author login
  • --app: Filter PRs by GitHub App author
  • --search: Apply GitHub issue/PR search syntax
  • --jq: (Optional) jq expression for filtering/transforming output. If omitted, returns schema info

Example Queries

Find large PRs (many changed files):

./query-prs.sh --jq '.[] | select(.changedFiles > 10) | {number, title, changedFiles}'

Get PRs awaiting review:

./query-prs.sh --jq '.[] | select(.reviewDecision == "REVIEW_REQUIRED") | {number, title, author: .author.login}'

Get PRs authored by GitHub Actions app activity context:

./query-prs.sh --app github-actions --jq '.[] | {number, title, author: .author.login}'

Find in-scope review feedback (team/collaborator + trusted automation):

# Trusted automation is matched by login; humans are matched by association.
./query-prs.sh --jq \
  '.[] | {number, title, reviews: [.reviews[]? | select(.author.login == "github-actions[bot]" or .author.login == "app/github-copilot" or .authorAssociation == "MEMBER" or .authorAssociation == "OWNER" or .authorAssociation == "COLLABORATOR")] }'

Ignore external review feedback:

./query-prs.sh --jq \
  '.[] | {number, title, external_reviews: [.reviews[]? | select(.authorAssociation == "CONTRIBUTOR" or .authorAssociation == "FIRST_TIME_CONTRIBUTOR" or .authorAssociation == "FIRST_TIMER" or .authorAssociation == "NONE")] }'

List PRs with their labels:

./query-prs.sh --jq '.[] | {number, title, labels: [.labels[].name]}'

Output Format

The script outputs JSON by default, making it easy to pipe through jq for additional processing.

Requirements

  • GitHub CLI (gh) authenticated
  • jq for filtering (installed by default on most systems)

How to use it

Copy the folder

Take github/github-pr-query from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.