GitHub CLI Assistant

Problem

CI checks, pull request status, and failed step logs are often spread across web pages, terminal output, and API responses. Manual triage can require switching between pages, copying run IDs, step names, and log fragments. The gh CLI covers many common operations, but practical use can still trip over repository context, command flags, and JSON field filtering.

How It Works

This skill organizes common GitHub workflows around the gh CLI, focused on terminal-based inspection and querying:
- Pull requests: check CI status on a PR, list recent workflow runs, and inspect failed steps in a run.
- Log triage: view logs for failed steps only, reducing noise from successful output.
- API queries: when subcommands do not expose the needed fields, use gh api to retrieve more precise data, such as selected PR fields.
- Structured output: many commands support --json, and you can filter fields with --jq for scripting or terminal analysis.

Boundaries

This is oriented toward command-line inspection of GitHub repositories rather than full GitHub service orchestration. Outside a git directory, specify --repo owner/repo or use URLs directly. Permission issues, secrets, organization policies, and deep CI debugging still depend on repository access and the CI platform's own diagnostics.