github-issue-query
Query GitHub issues with jq filtering and reusable selectors.
- License 许可
- MIT
- 所属仓库
- github/gh-aw
- 最近更新
- 2026-11-15
- Stars
- ★ 5.6k
- Forks
- 626
01 前言 Front Matter
- name
- github-issue-query
- description
- Query GitHub issues with jq filtering and reusable selectors.
02 资源文件 6
- 参考文档agents/openai.yaml139 B
- 参考文档GLOSSARY-FORMAT.md2.1 KB
- 参考文档LEARNING-RECORD-FORMAT.md2.7 KB
- 参考文档MISSION-FORMAT.md1.5 KB
- 脚本query-issues.sh3.9 KB
- 参考文档RESOURCES-FORMAT.md1.9 KB
03 SKILL.md 正文
GitHub Issue Query Skill
Query GitHub issues 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 issues from the current repository or any specified repository.
Basic Query (Returns Schema Only)
To list issues from the current repository:
./query-issues.sh
# Returns schema and data size, not full data
Get All Data
To get all issue data:
./query-issues.sh --jq '.'
With Repository
To query a specific repository:
./query-issues.sh --repo owner/repo
With jq Filtering
Use the --jq argument to filter and transform the output:
# Get only open issues
./query-issues.sh --jq '.[] | select(.state == "OPEN")'
# Get issue numbers and titles
./query-issues.sh --jq '.[] | {number, title}'
# Get issues by a specific author
./query-issues.sh --jq '.[] | select(.author.login == "username")'
# Get issues with specific label
./query-issues.sh --jq '.[] | select(.labels | map(.name) | index("bug"))'
# Count issues by state
./query-issues.sh --jq 'group_by(.state) | map({state: .[0].state, count: length})'
Common Options
--state: Filter by state (open, closed, all). Default: open--limit: Maximum number of issues 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 issues with many comments:
./query-issues.sh --jq '.[] | select(.comments.totalCount > 5) | {number, title, comments: .comments.totalCount}'
Get issues assigned to someone:
./query-issues.sh --jq '.[] | select(.assignees | length > 0) | {number, title, assignees: [.assignees[].login]}'
List issues with their labels:
./query-issues.sh --jq '.[] | {number, title, labels: [.labels[].name]}'
Get project board assignments:
./query-issues.sh --jq '.[] | {number, title, projects: [.projectItems.nodes[]? | .project?.url]}'
Find old issues (created over 30 days ago):
./query-issues.sh --jq '.[] | select(.createdAt < (now - 2592000 | strftime("%Y-%m-%dT%H:%M:%SZ")))'
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