What problem does it solve? Pushing code to GitHub often fails due to network restrictions, missing SSH host keys, or misconfigured remotes, and handling tokens in commands risks leaking credentials into logs or chat history. This Skill provides a safe, repeatable push and pull workflow that never exposes token values. ## Core Features & Use Cases - Credential-safe pushing: Uses SSH keys or an HTTPS token referenced only via environment variables, with output masked by sed so no secret ever appears in logs. - Automatic channel selection: Prefers SSH over port 443 and falls back to HTTPS with a token loaded from ~/.Renviron when SSH fails. - Troubleshooting guidance: Diagnoses common failures such as port 443 connection errors, host key verification issues, and publickey permission denials. - Use Case: After committing changes locally, ask the assistant to push to GitHub; it checks for unpushed commits, selects the working channel, pushes, and verifies the remote is up to date. ## Quick Start Push my local commits to GitHub and confirm the remote branch is up to date.