github-auth

To authenticate GitHub access, you can configure credentials using the gh CLI, HTTPS personal access tokens, or SSH keys. The skill automatically detects your system environment and selects the optimal authentication path based on existing credentials and installed tools.

Managing GitHub credentials involves leveraging environment detection to identify the best available authentication method. This skill resolves credential friction by supporting gh CLI, HTTPS tokens, and SSH keys to ensure secure interactions across diverse environments without manual intervention.

Yes, this GitHub authentication method supports both SSH keys and HTTPS personal access tokens, alongside the gh CLI. It implements robust detection logic to evaluate your system configuration and apply the most compatible authentication mechanism available.

You can verify your GitHub identity by asking the agent to check your current authentication status. This process ensures the agent has the necessary permissions configured via gh CLI, tokens, or SSH keys to clone private repositories and trigger CI pipelines.

You do not strictly need the gh CLI installed to automate GitHub authentication, as HTTPS tokens and SSH keys are also supported. However, having gh installed provides one of three detected authentication paths, maximizing compatibility for your automated workflows.

Yes, you can use this to configure GitHub authentication specifically for CI/CD operations. It securely facilitates automated repository management, issue tracking, and CI workflow interactions by establishing the necessary credentials across your development environment.