github-auth

GitHub authentication is configured by guiding HTTPS token, SSH key, and gh CLI workflows to establish secure repository access. The skill detects available methods and resolves GitHub user context to enable cloning, pushing, and managing repositories without repeated login failures.

Setting up GitHub access for an automation agent involves detecting available authentication methods and applying the best fit. The skill identifies HTTPS tokens, SSH keys, or API fallbacks, resolving repository context so agents can reliably perform pull request and issue operations.

The gh CLI is an optional integration for GitHub authentication, not a strict requirement. The skill detects available login methods and supports HTTPS tokens and SSH keys independently, applying gh CLI workflows only when the tool is present in the environment.

GitHub credential management distinguishes SSH keys and HTTPS tokens through environment detection logic. The skill evaluates the development environment for existing SSH keys or HTTPS tokens, selecting the optimal available authentication method to establish secure repository access.

Checking GitHub authentication status is supported by detecting configured credentials and resolving the active GitHub user context. The skill identifies whether HTTPS tokens, SSH keys, or gh CLI authentication is active, preventing login failures during repository push operations.

GitHub authentication fails during private repository cloning when no valid credentials are detected. The skill addresses this by applying authentication detection logic to identify and configure HTTPS tokens, SSH keys, or API fallbacks for secure repository access.