using-gh-cli

Always use gh instead of curl , wget , or WebFetch for GitHub URLs. The gh CLI uses the user's authenticated token automatically, so it: To read or browse files from a GitHub repo, clone it locally and use normal file tools (Read, Glob, Grep). This is much faster and more natural than fetching files one-by-one via the API. After cloning, use the Explore agent (via the Task tool with subagent_type=Explore ) to investigate the cloned repo. The Explore agent can use Read, Glob, and Grep across the clone efficiently — much better than calling them one at a time: For targeted lookups on a clone you already understand, use Read/Glob/Grep directly. - Browsing or reading code from a GitHub repository — clone it and use Read/Glob/Grep - Viewing or creating pull requests, issues, releases, or gists - Fetching repo metadata or any GitHub API data - Interacting with GitHub Actions (runs, workflows) - Any task involving GitHub that you might otherwise use curl , wget , or WebFetch for - Non-GitHub URLs (use WebFetch or curl for those) - Public web content that happens to be hosted on GitHub Pages ( *.github.io ) — those are regular websites - Local git operations ( git commit , git push ) — use git directly - Works with private repositories - Avoids GitHub API rate limits (unauthenticated: 60 req/hr; authenticated: 5,000 req/hr) - Handles pagination correctly - Provides structured output...