github-issue-query | Skill Performance & Reviews | TopRankSkills

TopRank Skills

Home / Skills / tools / github-issue-query

github-issue-query

maintained by githubnext

star 331 account_tree 37 verified_user MIT License
bolt View GitHub

name: github-issue-query description: Query GitHub issues efficiently with jq argument support for filtering

GitHub Issue Query Skill

This skill provides efficient querying of GitHub issues with built-in jq filtering support.

Important: jq Parameter is Optional

The --jq parameter is optional. When called without --jq, this skill returns schema and data size information instead of the full data. This prevents overwhelming responses with large datasets and helps you understand the data structure before querying.

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)

chat Comments (0)

chat_bubble_outline

No comments yet. Be the first to share your thoughts!

Skill Details

GitHub Stars 331
GitHub Forks 37
Created Jan 2026
Last Updated il y a 6 mois
tools tools git workflows

Related Skills

pr

pr

MoonshotAI
star 6.1k
chevron_right
feature-dev
chevron_right
drafting-pr
chevron_right
creating-pr
chevron_right
checking-docs
chevron_right

Build your own?

Join 12,000+ developers contributing to the Claude ecosystem.