gh-cli

Solid

Enforces authenticated gh CLI workflows over unauthenticated curl/WebFetch patterns. Use when working with GitHub URLs, API access, pull requests, or issues.

API & Backend 5,673 stars 496 forks Updated today CC-BY-SA-4.0

Install

View on GitHub

Quality Score: 88/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
52
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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 original Claude plugin implementation, see: - `plugins/gh-cli/README.md` - `plugins/gh-cli/hooks/`

Details

Author
trailofbits
Repository
trailofbits/skills
Created
4 months ago
Last Updated
today
Language
Python
License
CC-BY-SA-4.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category