github-discussion-query
Query GitHub discussions with jq filtering and reusable selectors.
- License 许可
- MIT
- 所属仓库
- github/gh-aw
- 最近更新
- 2026-11-15
- Stars
- ★ 5.6k
- Forks
- 626
01 前言 Front Matter
- name
- github-discussion-query
- description
- Query GitHub discussions with jq filtering and reusable selectors.
02 资源文件 2
- 脚本query-discussions.py5.1 KB
- 脚本query-discussions.sh3.4 KB
03 SKILL.md 正文
GitHub Discussion Query Skill
Query GitHub discussions 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 discussions from the current repository or any specified repository.
Basic Query (Returns Schema Only)
To list discussions from the current repository:
./query-discussions.sh
# Returns schema and data size, not full data
Get All Data
To get all discussion data:
./query-discussions.sh --jq '.'
With Repository
To query a specific repository:
./query-discussions.sh --repo owner/repo
With jq Filtering
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})'
Common Options
--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 info
Example Queries
Find 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}'
Output Format
The script outputs JSON by default, making it easy to pipe through jq for additional processing.
Requirements
- GitHub CLI (
gh) authenticated jqfor filtering (installed by default on most systems)
04 同仓库更多 Skills
cracktro
Edit, preview, and verify the standalone interactive talk deck in docs/public/cracktro (slides, SVG diagrams, transitions, WebAudio sound).
create-connector
Create or extend a declaration-only third-party connector, with narrow reads, separate safe outputs, optional protected triggers, and offline conformance evidence.
GitHub Agentic Workflows
GitHub Agentic Workflows (`gh-aw`) is a GitHub CLI extension for writing Agentic Workflows in markdown and compiling them to GitHub Actions.
windows-compatibility
Cross-platform path handling and command patterns
versioning-policy
Semver versioning rules for Squad SDK and CLI — prevents prerelease version incidents
tiered-memory
Three-tier agent memory model (hot/cold/wiki) for context reduction per spawn