github-issue-query

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

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:

Get issues assigned to someone:

List issues with their labels:

Get project board assignments:

Find old issues (created over 30 days ago):

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)