gh-cli
- 作者仓库星标 0
- 作者更新于 2026年8月25日 07:09
- 作者仓库 skills
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, 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/pullsFor the hook implementation, see:
plugins/gh-cli/README.mdplugins/gh-cli/hooks/
- 流狐分类
- 通用
- 作者声明 Agent
- 未找到明确声明；不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描，不代表运行安全
- 作者 / 版本 / 许可
- @trailofbits · 未声明 license
- 流狐 Token 估算
- 低消耗
- 流狐接入估算
- 即装即用
- 是否需要外部 API Key
- 未发现要求
- 检测到的系统要求
- 未声明
- 底层运行要求
- 未声明
- 检测到的文件与系统行为
-
- 只读
- 检测到的网络行为
- 允许外网请求
- 安装命令数
- 无（仅作为资料）
档案由构建时根据 SKILL.md 与安装命令自动衍生，可能与作者实际意图存在差异。
需要注意： 未限定 allowed-tools，默认拥有全部工具权限。
作者没有在当前 SKILL.md 中定义固定输出样例。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.
The target is not GitHub. Plain local git operations already solve the task.
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…
# 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/`作者原文负责流程事实；流狐只索引当前章节、要点、文件与命令。
章节 -> When to Use → When NOT to Use → Guidance
要点 -> - 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.
文件/命令 -> curl · wget · gh repo view · gh pr view · gh pr list · gh issue view · gh api · raw.githubusercontent.com
内容 SHA-256 -> d52bb616b30c
原文结构
适用与边界
原文中的明确线索
curl、wget、gh repo view、gh pr view、gh pr list、gh issue view、gh api、raw.githubusercontent.com