跳到正文
cccskills
免费在 GitHub 公开

github-pr-query

Query GitHub pull requests by author, status, or review needs, and extract selected fields as JSON. Inspect the data structure and size first, then use jq, a JSON filtering tool, to refine results.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

Query GitHub pull requests with jq filtering and reusable selectors.

集成工具GitHub
查看安装方法

适用场景

  • Find pull requests awaiting review
  • List pull request numbers and titles by author
  • Identify pull requests with many changed files
  • Count pull requests by state

包含的文件(2)

  • SKILL.md3.5 KB
  • query-prs.sh5.2 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

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)

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Coordinate work across AI agents with shared rules for locating team files, recording decisions and their reasons, and requesting help. It also defines who owns revisions after a reviewer rejects an artifact.

中文简介正在准备中。当前显示英语简介。

  • Locate team files across separate working directories
  • Record decisions that affect other agents
  • Request input from another specialist
github/gh-aw54222026年10月20日 更新

Set shared development rules for an agent team: keep specific agent names out of product code, tests, and CI configuration, verify affected tests before finishing, and record lessons learned from mistakes.

中文简介正在准备中。当前显示英语简介。

  • Share development rules across multiple agents
  • Keep team-specific agent names out of code and tests
  • Check affected tests before declaring work complete
github/gh-aw54222026年10月20日 更新

Routes requests to design, create, update, debug, or upgrade GitHub Agentic Workflows to the appropriate instructions. It helps the agent select a workflow-specific procedure and apply any additional rules defined for the repository.

中文简介正在准备中。当前显示英语简介。

  • Designing a new workflow through questions
  • Investigating failed runs and recurring errors
  • Upgrading workflows and addressing deprecations
github/gh-aw54222026年10月20日 更新

Prepare architecture proposals before implementation so the team can agree on a direction. Organize evidence, technical choices, effects on existing work, risks, and the first release’s scope into a document with clear recommendations and decision owners.

中文简介正在准备中。当前显示英语简介。

  • Proposing a major architecture change
  • Replanning milestones after a foundation change
  • Comparing technical options before seeking approval
github/gh-aw54222026年10月20日 更新

Update the gh-aw-firewall version used by gh-aw, rebuild generated files, and review release notes and configuration schemas, which define valid settings. It guides related code and test updates while identifying follow-up work that remains.

中文简介正在准备中。当前显示英语简介。

  • Updating the firewall version used by gh-aw
  • Reviewing release notes for integration changes
  • Checking configuration schema differences
github/gh-aw54222026年10月20日 更新

Review git and gh operations in gh-aw workflows to check credential availability for each repository. Identify missing token handoffs, risky expansions of limited checkouts, and error handling needed where credentials are intentionally unavailable.

中文简介正在准备中。当前显示英语简介。

  • Reviewing git operations after repository checkout
  • Checking tokens for private cross-repository access
  • Reviewing sparse and shallow checkout changes
github/gh-aw54222026年10月20日 更新

查看 github 的全部技能

报告此技能的问题