Back up to GitHub

Git records versions on your computer. GitHub can store a copy elsewhere. Set up both before provider keys and store credentials enter the workflow.

Prompt

Read agent-skills/setup-github-backup.md. Inspect the current repository, branch,
remotes, ignore rules, and uncommitted work. Make sure environment files, EAS
credentials, Apple keys, service-account JSON, keystores, and Supabase secrets
are ignored and absent from history. Prepare a clean first backup. Ask me before
creating/changing a GitHub remote or pushing.

Important safety rules

• Do not initialize a nested Git repository when the kit already lives inside one.
• Never reset or discard existing changes to make the status look clean.
• Do not paste a GitHub token into chat; use normal GitHub CLI or browser auth.
• Inspect staged files before every commit.
• Keep .env.local, server secret files, signing material, and downloaded credentials out of Git history—not just out of the latest commit.

For important projects, test the backup by cloning it into a temporary folder, installing dependencies, and running at least typecheck. A green GitHub page is not proof that ignored assets or setup instructions were included correctly.