gh cli
- Repo stars 0
- Author updated Aug 24, 2026, 11:09 PM
- Author repo skills
- Domain
- Other
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @trailofbits · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Network behavior
- External requests
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# gh-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`, or unauthenticated web fetches 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`, and `gh api` over unauthenticated `curl` or `wget`.
- Prefer cloning a repository and reading files locally over fetching `raw.githubusercontent.com` blobs directly.
- Avoid using GitHub API `/contents/` endpoints as a substitute for cloning and reading repository files.
Examples:
```sh
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.md`
- `plugins/gh-cli/hooks/`
Sections and files
Listed in source order.
sections -> When to Use → When NOT to Use → Guidance
terms -> - Working with GitHub repositories, pull requests, issues, releases, or raw file URLs. · - The target is not GitHub. · Prefer the authenticated gh CLI over raw HTTP fetches for GitHub content. · - Prefer gh repo view, gh pr view, gh pr list, gh issue view, and gh api over unauthenticated curl or wget.
files/cmd -> curl · wget · gh repo view · gh pr view · gh pr list · gh issue view · gh api · raw.githubusercontent.com
body sha256 -> d52bb616b30c
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, or unauthenticated web fetches against GitHub.When NOT to Use
The target is not GitHub. Plain local git operations already solve the task.
Guidance
Prefer the authenticated
ghCLI over raw HTTP fetches for GitHub content. In particular: Prefergh repo view,gh pr view,gh pr list,gh issue view, andgh apiover unauthenticatedcurlorwget. Prefer cloning a repository and reading files locally over fetchingraw.githubusercontent.comblobs directly. Avoid using GitHub API/contents/endpoints as a substitute for cloning and reading repository files.