بنقرة واحدة
github-issue-query
Query GitHub issues with jq filtering and reusable selectors.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Query GitHub issues with jq filtering and reusable selectors.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Conversational skill that interviews users to design new agentic workflows
Route gh-aw workflow design/create/debug/upgrade requests to the right prompts.
Analyze and reduce token consumption in agentic workflows — guardrail-specific entry points, measurement, and optimization techniques.
Implement secret-safe HTTP headers for MCP transport in gh-aw.
Review code that performs git or gh operations against repository checkouts in gh-aw, checking that the right credentials are available at the right time and that sparseness, shallowness and credential-free factors are properly considered.
Teach Copilot how to plan, address, and respond to pull request review feedback.
| name | github-issue-query |
| description | Query GitHub issues with jq filtering and reusable selectors. |
Query GitHub issues efficiently with built-in jq filtering.
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.
Use this skill to query issues from the current repository or any specified repository.
To list issues from the current repository:
./query-issues.sh
# Returns schema and data size, not full data
To get all issue data:
./query-issues.sh --jq '.'
To query a specific repository:
./query-issues.sh --repo owner/repo
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})'
--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 infoFind 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")))'
The script outputs JSON by default, making it easy to pipe through jq for additional processing.
gh) authenticatedjq for filtering (installed by default on most systems)