GitHub CLI
VerifiedInteract with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
$ Add to .claude/skills/ About This Skill
# GitHub Skill
Use the `gh` CLI to interact with GitHub. Always specify `--repo owner/repo` when not in a git directory, or use URLs directly.
Pull Requests
Check CI status on a PR:
```bash gh pr checks 55 --repo owner/repo ```
List recent workflow runs:
```bash gh run list --repo owner/repo --limit 10 ```
View a run and see which steps failed:
```bash gh run view <run-id> --repo owner/repo ```
View logs for failed steps only:
```bash gh run view <run-id> --repo owner/repo --log-failed ```
API for Advanced Queries
The `gh api` command is useful for accessing data not available through other subcommands.
Get PR with specific fields:
```bash gh api repos/owner/repo/pulls/55 --jq '.title, .state, .user.login' ```
JSON Output
Most commands support `--json` for structured output. You can use `--jq` to filter:
```bash gh issue list --repo owner/repo --json number,title --jq '.[] | "\(.number): \(.title)"' ```
Use Cases
- Interact with GitHub issues, PRs, and CI runs using the gh CLI tool
- Check CI/CD status on pull requests and trigger workflow re-runs
- Query the GitHub API for advanced repository data and custom reports
- Manage pull request reviews, labels, and merge operations from the terminal
- Automate GitHub issue creation and management through CLI commands
Pros & Cons
Pros
- +Compatible with multiple platforms including claude-code, openclaw
- +Well-documented with detailed usage instructions and examples
- +Open source with permissive licensing for commercial use
Cons
- -No built-in analytics or usage metrics dashboard
- -Configuration may require familiarity with git & version control concepts
FAQ
What does GitHub CLI do?
What platforms support GitHub CLI?
What are the use cases for GitHub CLI?
100+ free AI tools
Writing, PDF, image, and developer tools — all in your browser.
Next Step
Use the skill detail page to evaluate fit and install steps. For a direct browser workflow, move into a focused tool route instead of staying in broader support surfaces.