github-discussion-query

Query GitHub Discussions with optional jq filtering and schema previews.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/az9713/gh-aw --skill github-discussion-query-az9713
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-discussion-query
Source: https://github.com/az9713/gh-aw/tree/main/skills/github-discussion-query
Command: npx skills add https://github.com/az9713/gh-aw --skill github-discussion-query-az9713

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub Discussions can be noisy; this skill provides efficient querying with optional jq filtering to retrieve schema and metadata when data would be too large, making targeted results easier to obtain.

Core Features & Use Cases

  • Built-in jq filtering to shape results and extract fields like number, title, author, category, labels, and answers.
  • Query from the current repository or any specified repository with optional --repo and --limit controls.
  • Safe by default: without --jq it returns a schema and size information to help understand data structure before querying.

Quick Start

Run the provided query script with the narrow --jq filter to preview the data structure.

Frequently Asked Questions about github-discussion-query

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I query GitHub discussions and filter specific fields from the results?

You can query GitHub discussions and filter specific fields by using the `--jq` option. This allows you to pass jq filters to extract data like number, title, author, category, labels, and answers directly from the JSON output.

Can I fetch GitHub discussions from a repository other than my current working directory?

Yes, you can fetch GitHub discussions from any specified repository by using the `--repo` flag. Without this flag, the query defaults to fetching discussion data from your current repository.

Do I need jq installed to query GitHub discussions with this tool?

Yes, jq is required for filtering and transforming the JSON data fetched by the GitHub CLI. While you can run a query without the `--jq` flag to see schema information, jq is essential for extracting targeted results.

What is the best way to preview the data structure before extracting GitHub discussions?

The best way to preview the data structure is to run a query without the `--jq` filter. By default, this safe mode returns schema and size information, helping you understand the data structure before querying large datasets.

How do I limit the number of GitHub discussions returned in a single query?

You can limit the number of GitHub discussions returned by using the `--limit` control. This helps manage the volume of JSON data fetched from the repository and keeps your query results targeted.

Why does my GitHub discussions query return schema information instead of the actual data fields?

Your query returns schema information because it was run without the `--jq` flag. This default behavior prevents retrieving excessively large datasets, allowing you to inspect the data structure before applying jq filters.