Query GitHub Discussions and extract titles, authors, categories, or answer status. First inspect the data structure and size, then use jq, a JSON filtering tool, to select relevant discussions, sort updates, or count entries by category.
中文简介正在准备中。当前显示英语简介。
Query GitHub discussions with jq filtering and reusable selectors.
安装前可以查看交给 AI 代理的指令内容。
Query GitHub discussions efficiently with built-in jq filtering.
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.
Use this skill to query discussions from the current repository or any specified repository.
To list discussions from the current repository:
./query-discussions.sh
# Returns schema and data size, not full data
To get all discussion data:
./query-discussions.sh --jq '.'
To query a specific repository:
./query-discussions.sh --repo owner/repo
Use the --jq argument to filter and transform the output:
# Get discussion numbers and titles
./query-discussions.sh --jq '.[] | {number, title}'
# Get discussions by a specific author
./query-discussions.sh --jq '.[] | select(.author.login == "username")'
# Get discussions in a specific category
./query-discussions.sh --jq '.[] | select(.category.name == "Ideas")'
# Get answered discussions
./query-discussions.sh --jq '.[] | select(.answer != null)'
# Count discussions by category
./query-discussions.sh --jq 'group_by(.category.name) | map({category: .[0].category.name, count: length})'
--limit: Maximum number of discussions 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 infoFind discussions with many comments:
./query-discussions.sh --jq '.[] | select(.comments.totalCount > 5) | {number, title, comments: .comments.totalCount}'
Get unanswered discussions:
./query-discussions.sh --jq '.[] | select(.answer == null) | {number, title, category: .category.name}'
List discussions with their labels:
./query-discussions.sh --jq '.[] | {number, title, labels: [.labels[].name]}'
Find discussions by category:
./query-discussions.sh --jq '.[] | select(.category.name == "Q&A") | {number, title, author: .author.login}'
Get recently updated discussions:
./query-discussions.sh --jq 'sort_by(.updatedAt) | reverse | .[0:10] | .[] | {number, title, updatedAt}'
The script outputs JSON by default, making it easy to pipe through jq for additional processing.
gh) authenticatedjq for filtering (installed by default on most systems)还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
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.
中文简介正在准备中。当前显示英语简介。
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.
中文简介正在准备中。当前显示英语简介。
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.
中文简介正在准备中。当前显示英语简介。
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.
中文简介正在准备中。当前显示英语简介。
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.
中文简介正在准备中。当前显示英语简介。
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.
中文简介正在准备中。当前显示英语简介。