deploy-credentialslisted

# Deploy Credentials GitHub and Cloudflare credentials are **optional**. They may be pre-configured via Settings > Push & Deploy, but many users will not have them set. This skill carries the env-var table, the operations they enable, and the check-then-fallback protocol. ## Environment Variables Only present if the user configured them in Settings. Always check before assuming they exist. | Variable | What it enables | |---|---| | `GH_TOKEN` | GitHub fine-grained PAT. Auto-detected by `gh` CLI and git credential helper. | | `CLOUDFLARE_API_TOKEN` | Cloudflare API token. Auto-detected by `wrangler` CLI. | | `CLOUDFLARE_ACCOUNT_ID` | Cloudflare account ID. Auto-detected by `wrangler` CLI. | ## What you can do with GH_TOKEN When `GH_TOKEN` is set, all of the following work without any manual auth: **Git operations:** - `git push`, `git pull`, `git clone` (HTTPS remotes, auto-authenticated via credential helper) - `git push -u origin HEAD` (set upstream and push) **Repository management:** - `gh repo create <name> --public --source=. --remote=origin --push` - `gh repo clone <owner>/<repo>` - `gh repo delete <owner>/<repo> --yes` - `gh repo list` (find user's repositories) **Pull requests:** - `gh pr create --title "..." --body "..."` - `gh pr list`, `gh pr view`, `gh pr merge` **CI / GitHub Actions:** - `gh run list`, `gh run view <id>`, `gh run view <id> --log-failed` - `gh run cancel <id>` (cancel stale CI runs) - `gh secret set <name>` (set repository secrets for CI