github-pr-query
Query GitHub pull requests efficiently with jq argument support for filtering
Best use case
github-pr-query is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Query GitHub pull requests efficiently with jq argument support for filtering
Teams using github-pr-query should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/github-pr-query/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How github-pr-query Compares
| Feature / Agent | github-pr-query | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Query GitHub pull requests efficiently with jq argument support for filtering
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
AI Agents for Startups
Explore AI agent skills for startup validation, product research, growth experiments, documentation, and fast execution with small teams.
SKILL.md Source
# GitHub Pull Request Query Skill
This skill provides efficient querying of GitHub pull requests with built-in jq filtering support.
## Important: jq Parameter is Optional
The `--jq` parameter is **optional**. When called without `--jq`, this skill returns **schema and data size information** instead of the full data.
This prevents overwhelming responses with large datasets and helps you understand the data structure before querying.
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:
```bash
./query-prs.sh
# Returns schema and data size, not full data
```
### Get All Data
To get all PR data:
```bash
./query-prs.sh --jq '.'
```
### With Repository
To query a specific repository:
```bash
./query-prs.sh --repo owner/repo
```
### With jq Filtering
Use the `--jq` argument to filter and transform the output:
```bash
# 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
- `--jq`: (Optional) jq expression for filtering/transforming output. If omitted, returns schema info
### Example Queries
**Find large PRs (many changed files):**
```bash
./query-prs.sh --jq '.[] | select(.changedFiles > 10) | {number, title, changedFiles}'
```
**Get PRs awaiting review:**
```bash
./query-prs.sh --jq '.[] | select(.reviewDecision == "REVIEW_REQUIRED") | {number, title, author: .author.login}'
```
**List PRs with their labels:**
```bash
./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)Related Skills
github-script
Best practices for writing JavaScript code for GitHub Actions using github-script
github-mcp-server
GitHub MCP Server Documentation
github-issue-query
Query GitHub issues efficiently with jq argument support for filtering
github-discussion-query
Query GitHub discussions efficiently with jq argument support for filtering
github-copilot-agent-tips-and-tricks
Tips and Tricks for Working with GitHub Copilot Agent PRs
temporary-id-safe-output
Plan for adding temporary ID support to safe output jobs
skills
Using Skillz MCP Server with Docker
reporting
Guidelines for formatting reports using HTML details/summary tags
messages
Instructions for adding new message types to the safe-output messages system
javascript-refactoring
Instructions for refactoring JavaScript code into separate files
http_mcp_headers
HTTP MCP Header Secret Support - Implementation Summary
gh-agent-task
GitHub CLI Agent Task Extension