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.
The GitHub skill allows users to interact with GitHub repositories through the `gh` CLI. It provides a command-line interface to manage and access data related to GitHub projects, such as pull requests (PRs), issues, continuous integration (CI) runs, and advanced queries using the GitHub API. This skill helps users who prefer the terminal for automating and simplifying their GitHub workflows by offering powerful commands to interact with various aspects of their repositories directly from the command line.
The skill includes commands for managing pull requests, checking CI statuses, listing workflow runs, viewing detailed logs, and interacting with the GitHub API for more complex queries. Users can also take advantage of JSON outputs for structured data retrieval and filtering using `--jq`. The ability to directly query GitHub's REST API allows for advanced actions like fetching specific fields of a pull request. This skill streamlines repository management, making it an essential tool for developers, DevOps teams, and anyone looking to automate or simplify interactions with GitHub.
Typical users include developers, continuous integration engineers, and project managers who are managing GitHub repositories or need to integrate GitHub operations into automated workflows. It's ideal for users who are comfortable using the command line and want to streamline their GitHub tasks without switching to a web interface.
You can check the CI status of a pull request by running the command `gh pr checks <pr-id> --repo owner/repo`.
Yes, you can view logs for failed steps only by using the command `gh run view <run-id> --repo owner/repo --log-failed`.
The `gh api` command is used for making advanced queries to access data not available through other `gh` subcommands. For example, you can fetch specific fields of a pull request.
Yes, many commands support `--json` for structured output, and you can use `--jq` to filter and format the results.
No, but when not in a git directory, you must always specify `--repo owner/repo` to indicate the repository you want to interact with.
Quick Setup:
.claude/skills/Repository
mitsuhiko/agent-stuff