github-issue-query
Query GitHub issues with jq filtering and reusable selectors.
How do I install this agent skill?
npx skills add https://github.com/github/gh-aw --skill github-issue-queryIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill provides a shell script to query GitHub issues using the GitHub CLI and filter results with jq. It follows security best practices by using proper quoting for arguments and focusing on a specific, non-destructive read-only task.
- Socketpass
No alerts
- Snykwarn
Risk: MEDIUM · 1 issue
What does this agent skill do?
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)
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/github/gh-aw/github-issue-query">View github-issue-query on skillZs</a>