github-auth

GitHub authentication for automated agents unifies SSH key and HTTPS token methods. This skill automatically detects available credentials and configures secure access to repositories, PRs, and issues across local and CI environments.

Setting up GitHub CLI access for CI environments requires configuring a GitHub token with safe credential handling. This skill provides automated setup flows with fallback options to ensure reliable gh CLI authentication during automated workflows.

Yes, GitHub authentication works with both git and gh CLI tools. The skill automatically detects which tooling is installed and selects the appropriate authentication path, supporting HTTPS token-based access for git and gh CLI authentication simultaneously.

GitHub token authentication failures often stem from misconfigured environment access or unsafe credential handling. This skill troubleshoots authentication paths, enforces safe credential practices, and provides fallback options to resolve access issues to repositories and PRs.

Automating PR management workflows requires either a configured GitHub token for HTTPS or an SSH key for secure access. The skill detects your available authentication method and establishes the appropriate connection for managing PRs and issues.

Yes, you can use SSH keys for GitHub authentication instead of HTTPS tokens. This skill supports both methods, automatically detects your available authentication path, and provides flexible setup flows with safe credential handling and fallback options.