mcpField
G
github-issue-query

github-issue-query

github.com/githubDevelopment5.5k55 installsUpdated today
Repository

About github-issue-query

A skill for querying GitHub issues with optional jq filtering. It can target the current or a specified repository, and returns schema and data-size information by default to help scope results before retrieving full data.

Key features

  1. 01Query current or specified repository
  2. 02Filter issues by state and limit
  3. 03Apply jq filters to JSON output
  4. 04Return schema and size by default

Use cases

  1. 01Inspect issue data structure before querying
  2. 02Find issues matching custom criteria
  3. 03Extract selected fields from issue results

MCP support

The input does not describe an MCP connection or server.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/github/gh-aw --skill github-issue-query

After installing, type/github-issue-queryin Claude Code to confirm it loaded.

Bundled filesquery-issues.sh

Details

From the project README

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
  • jq for filtering (installed by default on most systems)

Comments

Markdown supported