About gh-cli
A skill for using GitHub's authenticated `gh` CLI when working with repositories, pull requests, issues, releases, and files. It guides users toward CLI or local-clone access instead of unauthenticated HTTP fetching.
Key features
- 01Prefer authenticated `gh` commands
- 02View repositories, pull requests, and issues
- 03Query GitHub with `gh api`
- 04Clone and inspect files locally
Use cases
- 01Reviewing a GitHub pull request or issue
- 02Accessing private repository content
- 03Avoiding raw HTTP fetches for GitHub data
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ trailofbits/ skills --skill gh-cliAfter installing, type/gh-cliin Claude Code to confirm it loaded.
Bundled filesagents/openai.yamlassets/trail-of-bits-mark.svg
Details
From the project READMEgh-cli
When to Use
- Working with GitHub repositories, pull requests, issues, releases, or raw file URLs.
- You need authenticated access to private repositories or higher API rate limits.
- You are about to use
curl,wget,WebFetch, or an MCP fetch tool against GitHub.
When NOT to Use
- The target is not GitHub.
- Plain local git operations already solve the task.
Guidance
Prefer the authenticated gh CLI over raw HTTP fetches for GitHub content. In particular:
- Prefer
gh repo view,gh pr view,gh pr list,gh issue view, andgh apiover unauthenticatedcurlorwget. - Prefer cloning a repository and reading files locally over fetching
raw.githubusercontent.comblobs directly. - Avoid using GitHub API
/contents/endpoints as a substitute for cloning and reading repository files.
Examples:
gh repo view owner/repo
gh pr view 123 --repo owner/repo
gh api repos/owner/repo/pulls
For the hook implementation, see:
plugins/gh-cli/README.mdplugins/gh-cli/hooks/
Comments
Markdown supported