Debug GitHub CI/CD and Pull Requests

Uses the gh CLI to interact with GitHub - issues, pull requests, workflow runs, and CI failures - always specifying --repo owner/repo when not run inside a git directory. It defines a four-step sequence for debugging a failing CI run: check PR status to identify which checks are failing (gh pr checks 55 --repo owner/repo), list recent workflow runs to find the relevant run ID (gh run list --repo owner/repo --limit 10), view the failed run to see which jobs and steps failed (gh run view <run-id> --repo owner/repo), and fetch detailed logs for just the failed steps (gh run view <run-id> --repo owner/repo --log-failed).

Use it when the user asks about GitHub issues, pull requests, workflow runs, or CI failures, or when you need gh issue, gh pr, gh run, or gh api from the command line rather than the GitHub web UI. It's a CLI-driven investigation workflow, not a GitHub API client library - for data not exposed through the dedicated subcommands, it falls back to gh api directly.

gh pr checks 55 --repo owner/repo

For advanced queries beyond the dedicated subcommands, gh api hits the REST API directly, e.g. gh api repos/owner/repo/pulls/55 --jq '.title, .state, .user.login' to pull specific fields off a PR. Most commands also support --json for structured output, which can be piped into --jq for filtering, e.g. gh issue list --repo owner/repo --json number,title --jq '.[] | "\(.number): \(.title)"' to print a compact number-and-title list.

Wraps the official gh CLI's issue, pr, run, and api subcommands against GitHub's REST API, using --repo owner/repo or direct URLs to target a repository outside the current git directory.

Developers who want to check PR status, list and inspect CI workflow runs, pull failure logs, or query GitHub data via gh api/--json/--jq without leaving the terminal.