github-auth

Configure GitHub authentication by setting up git-based HTTPS tokens or SSH keys for repository access, or by integrating gh CLI authentication for API operations. The skill detects existing credentials and guides setup across local, remote, and CI environments.

The gh CLI is optional for GitHub authentication. The skill integrates gh CLI for richer API access when installed, but automatically detects its absence and provides fallback flows using git-based HTTPS tokens or SSH keys.

Automate GitHub access without manual login by configuring passwordless HTTPS tokens or SSH keys for git operations, or by using gh CLI authentication for API access. The skill detects existing authentication status and applies the appropriate method automatically.

Yes, SSH keys are supported for GitHub authentication in CI environments. The skill covers git-based SSH credentials alongside HTTPS tokens, with automatic detection and fallback paths across local, remote, and CI environments.

Automated agents fail to access GitHub repositories without valid authenticated sessions. The skill requires git, optionally gh CLI, and curl-capable tooling along with valid credentials or tokens to establish access for repo operations, PRs, and CI interactions.

Setting up GitHub authentication requires git and curl-capable tooling as dependencies, with gh CLI being optional. Valid credentials such as HTTPS tokens or SSH keys are also needed to establish authenticated sessions across environments.