github-issue-query
Tool for filtering GitHub issues with jq syntax support.
Install
mkdir -p .claude/skills/github-issue-query && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/3225" && unzip -o skill.zip -d .claude/skills/github-issue-query && rm skill.zipInstalls to .claude/skills/github-issue-query
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Query GitHub issues with jq filtering and reusable selectors.Key capabilities
- →List issues from current or specified repositories
- →Filter issues by state, author, or labels
- →Transform output using jq expressions
- →Group issues by state and count
- →Inspect issue schema and data size
How it works
The skill wraps the GitHub CLI to fetch issue data and pipes it through jq for filtering and transformation based on user-provided expressions.
Inputs & outputs
When to use github-issue-query
- →Finding issues assigned to a specific user
- →Filtering issues by label and creation date
- →Extracting status updates from a list of open issues
About this skill
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)
When not to use it
- →Non-GitHub issue tracking systems
Prerequisites
Limitations
- →Dependent on GitHub CLI authentication
- →Requires knowledge of jq syntax for advanced filtering
How it compares
It provides a programmatic interface for querying GitHub issues that is more precise than standard CLI list commands.
Compared to similar skills
github-issue-query side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| github-issue-query (this skill) | 1 | 3mo | Review | Beginner |
| zai-cli | 5 | 6mo | Review | Beginner |
| prompt-analysis | 8 | 4mo | Review | Beginner |
| retro | 0 | 4mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by githubnext
View all by githubnext →You might also like
zai-cli
numman-ali
Z.AI CLI providing: - Vision: image/video analysis, OCR, UI-to-code, error diagnosis (GLM-4.6V) - Search: real-time web search with domain/recency filtering - Reader: web page to markdown extraction - Repo: GitHub code search and reading via ZRead - Tools: MCP tool discovery and raw calls - Code: TypeScript tool chaining Use for visual content analysis, web search, page reading, or GitHub exploration. Requires Z_AI_API_KEY.
prompt-analysis
git-ai-project
Analyze AI prompting patterns and acceptance rates
retro
MrUnreal
Data-driven retrospective from git history. Analyzes commits, contributors, and trends. Produces actionable reports.
github-project-board-generate-board-analytics
vamseeachanta
Sub-skill of github-project-board: Generate Board Analytics.
markitdown
K-Dense-AI
Convert various file formats (PDF, Office documents, images, audio, web content, structured data) to Markdown optimized for LLM processing. Use when converting documents to markdown, extracting text from PDFs/Office files, transcribing audio, performing OCR on images, extracting YouTube transcripts, or processing batches of files. Supports 20+ formats including DOCX, XLSX, PPTX, PDF, HTML, EPUB, CSV, JSON, images with OCR, and audio with transcription.
pdf-processing
Ming-Kai-LC
Comprehensive PDF processing techniques for handling large files that exceed Claude Code's reading limits, including chunking strategies, text/table extraction, and OCR for scanned documents. Use when working with PDFs larger than 10-15MB or more than 30-50 pages.