Query GitHub issues with jq filtering and reusable selectors.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add github/gh-aw --skill github-issue-query --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Github Issue Query?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/github-github-issue-query-gh-aw)More formats (shields.io, HTML) on the badges page.
---
name: github-issue-query
description: Query GitHub issues with jq filtering and reusable selectors.
---
# 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:
```bash
./query-issues.sh
# Returns schema and data size, not full data
```
### Get All Data
To get all issue data:
```bash
./query-issues.sh --jq '.'
```
### With Repository
To query a specific repository:
```bash
./query-issues.sh --repo owner/repo
```
### With jq Filtering
Use the `--jq` argument to filter and transform the output:
```bash
# 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:**
```bash
./query-issues.sh --jq '.[] | select(.comments.totalCount > 5) | {number, title, comments: .comments.totalCount}'
```
**Get issues assigned to someone:**
```bash
./query-issues.sh --jq '.[] | select(.assignees | length > 0) | {number, title, assignees: [.assignees[].login]}'
```
**List issues with their labels:**
```bash
./query-issues.sh --jq '.[] | {number, title, labels: [.labels[].name]}'
```
**Get project board assignments:**
```bash
./query-issues.sh --jq '.[] | {number, title, projects: [.projectItems.nodes[]? | .project?.url]}'
```
**Find old issues (created over 30 days ago):**
```bash
./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)
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!