github-pr-query

Query GitHub pull requests with jq filters and return JSON or schema summaries.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/kaushal-waygood/agentic-self-healing-ci --skill github-pr-query-kaushal-waygood
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr-query
Source: https://github.com/kaushal-waygood/agentic-self-healing-ci/tree/main/skills/github-pr-query
Command: npx skills add https://github.com/kaushal-waygood/agentic-self-healing-ci --skill github-pr-query-kaushal-waygood

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents overwhelming responses when listing pull requests by returning a concise schema and data-size summary by default and enabling targeted data retrieval only when the user supplies an explicit jq filter. It helps developers and maintainers explore PR metadata safely and efficiently before requesting full datasets.

Core Features & Use Cases

  • Schema preview: When no jq filter is provided, the skill returns item counts, byte size, and a documented schema so you can understand the data shape without fetching everything.
  • Flexible jq filtering: Apply arbitrary jq expressions to filter, transform, and extract only the fields you need (for example, open PRs, large changes, or PRs by author).
  • Repository and state controls: Query the current repository or any OWNER/REPO and filter by state and limit to scope results for audits, release checks, or triage workflows.
  • Use Case: Inspect recent merged PRs from a specific contributor, count PRs by state, or list PR numbers and titles for release notes.

Quick Start

Run the query-prs.sh script with --jq '.' to retrieve all pull request data for the current repository.

Frequently Asked Questions about github-pr-query

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

FAQPage Schema
How do I filter GitHub pull requests without downloading massive JSON responses?

To filter GitHub pull requests safely, return a concise schema and data-size summary by default, then apply explicit jq client-side filtering to extract only the fields you need.

What's the best way to inspect recent merged PRs from a specific contributor using gh CLI?

The best way to inspect recent merged PRs from a specific contributor is using gh CLI with jq expressions to query the repository and filter pull request metadata by state and author.

Do I need jq to list pull requests from a different owner or repository?

You do not need jq to list pull requests from a different owner or repository, but omitting jq returns a documented schema summary instead of full data retrieval.

Can I count GitHub pull requests by state for release checks or triage workflows?

Yes, you can count GitHub pull requests by state for release checks or triage workflows by applying flexible jq filters against the gh CLI JSON output.

Why does listing pull requests with gh CLI return a schema instead of full data?

Listing pull requests with gh CLI returns a schema instead of full data to prevent overwhelming responses, providing item counts and byte size unless an explicit jq filter is supplied.