Github Auth

GitHub Auth

Overview

Choose the least surprising GitHub auth path for the current machine, then verify it before doing repository work.

Workflow

1. Check what is installed:

git --version
gh --version 2>/dev/null || true
gh auth status 2>/dev/null || true

1. Prefer an already-authenticated gh session when available.
2. If gh is not authenticated, ask the user to complete gh auth login.
3. If gh is unavailable, use normal git credentials or SSH.
4. Configure commit identity only when needed:

git config --global user.name "Your Name"
git config --global user.email "you@example.com"

1. Verify with a read-only command before pushing:

git ls-remote origin

Safety

• Never paste tokens into committed files.
• Prefer credential helpers or gh auth login over token-in-remote URLs.
• Do not print full secrets in summaries, logs, screenshots, or pull requests.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: Martin-Hausleitner
• Source: Martin-Hausleitner/martins-awesome-skills
• License: MIT

Install and usage instructions live in the source repository linked above.