Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
88
85%
Does it follow best practices?
Impact
100%
1.23xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Use the gh CLI to interact with GitHub. Always specify --repo owner/repo when not in a git directory, or use URLs directly.
Check CI status on a PR:
gh pr checks 55 --repo owner/repoList recent workflow runs:
gh run list --repo owner/repo --limit 10View a run and see which steps failed:
gh run view <run-id> --repo owner/repoView logs for failed steps only:
gh run view <run-id> --repo owner/repo --log-failedThe gh api command is useful for accessing data not available through other subcommands.
Get PR with specific fields:
gh api repos/owner/repo/pulls/55 --jq '.title, .state, .user.login'Most commands support --json for structured output. You can use --jq to filter:
gh issue list --repo owner/repo --json number,title --jq '.[] | "\(.number): \(.title)"'851150f
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.