Github

• You want an agent to monitor or triage GitHub issues and pull requests on your behalf.
• You need to inspect CI/CD pipeline status — listing workflow runs, viewing failed step logs, or diagnosing a broken build.
• You need structured JSON output from GitHub for downstream processing or reporting.
• You want to query GitHub REST API endpoints that go beyond what standard gh subcommands expose (e.g. fetching specific PR fields with --jq filters).

• You need to interact with GitHub at a Git protocol level (cloning, pushing commits, rebasing) — this skill is for the GitHub platform API, not raw Git operations.
• You require a GitLab, Bitbucket, or other non-GitHub host; the gh CLI is GitHub-only.

List, view, and check the status of pull requests with commands like gh pr checks and gh pr list. Always works against any repo by specifying --repo owner/repo, even outside a git directory.

Inspect GitHub Actions workflow runs with gh run list, gh run view, and --log-failed to surface only the failing step logs. Ideal for agents that need to diagnose broken pipelines without manual log hunting.

The gh api command unlocks any GitHub REST API endpoint. Combine it with --jq filters to extract exactly the fields you need — for example, pulling a PR's title, state, and author in one call.

Most gh subcommands support --json flags so responses can be piped into --jq expressions or consumed directly by downstream tools. This makes it straightforward for agents to parse and act on GitHub data programmatically.

List and filter issues with gh issue list, including JSON output for structured queries. Supports filtering by labels, state, assignee, and more through standard gh flags.

An agent checks all open PRs, fetches their CI status via gh pr checks, and surfaces any PRs that are failing or stalled — giving the developer a prioritized list without manual dashboard checking.

When a build breaks, the agent runs gh run view <run-id> --log-failed to pull only the failed step logs and summarizes the root cause, saving engineers from scrolling through lengthy CI output.

The agent queries open issues with gh issue list --json and --jq filters to generate a structured report — grouping by label, age, or assignee — for a weekly team digest.

Using gh api with custom --jq queries, an agent retrieves specific metadata (e.g., PR merge commit SHA, reviewer list, or workflow timing) that isn't surfaced through standard subcommands.