GitHub CLI Query Assistant

What Problem It Solves

When GitHub PR, CI, and workflow status are scattered across pages, checking them in a browser is slow. The gh CLI can query PRs, runs, steps, and logs directly, but common flags such as --repo owner/repo, --json, and --jq are easy to forget. This skill organizes those query paths into a reusable workflow for day-to-day GitHub triage in the terminal.

How It Works

The skill is centered on the gh CLI: identify the target repository first, using --repo owner/repo outside a git directory or using a repository URL directly. Then check CI status on a PR, list recent workflow runs, inspect failed steps in a specific run, and retrieve only the failed-step logs. For data not covered by normal subcommands, it points to gh api for advanced queries, then uses --json for structured output and --jq to filter fields.

Boundaries

It assumes gh CLI is available and the user has GitHub access. It does not cover full repository creation, merging, or administration, and it does not replace local git operations. Query depth depends on account permissions, API rate limits, and log availability; enterprise or SSO environments may require separate authentication setup.