gh-cli

Using the gh CLI for authenticated GitHub workflows prevents unauthenticated rate limits when accessing private repositories, API endpoints, and raw content. It maps GitHub URLs to gh commands for deterministic, authenticated access to commits, issues, and pull requests.

Unauthenticated curl requests to api.github.com fail due to strict GitHub rate limits. Using the gh CLI authenticates requests automatically, providing consistent access to repository trees, releases, and Actions data without hitting unauthenticated traffic thresholds.

Using the gh CLI with shallow clones for file access is the best way to read files from private repositories programmatically. This authenticated method replaces raw.githubusercontent.com URLs, ensuring deterministic access to repository content while maintaining GitHub authentication.

You need to install and authenticate the gh CLI before using GitHub CLI workflows. The skill requires gh to be installed and authenticated to access GitHub data, falling back to ordinary web access only when gh is unavailable with clear guardrails.

You can use gh CLI to fetch pull requests, issues, and releases instead of raw GitHub URLs. Helper scripts map GitHub URLs to gh commands, ensuring authenticated and deterministic workflows for accessing repository data, commits, and GitHub Actions.

You should fall back to ordinary web access only when gh is unavailable or unauthenticated. The skill provides clear guardrails and guidance for switching back to gh, ensuring authenticated GitHub workflows remain the default for accessing repos, files, and API endpoints.