local-app-github-publishing

Local App GitHub Publishing

Use this when the user asks to push a local app/prototype/project to GitHub for the first time, especially Electron, iOS/Xcode, mobile, desktop, or AI/API-integrated apps.

This skill complements the protected github-repo-management skill with the user-specific first-push hygiene: publish the useful source, not the machine's junk drawer wearing a trench coat.

Core Rule

Before the first commit, sanitize and verify. Generated builds, dependency folders, local Xcode state, and API credentials do not belong in the initial history.

Default Behavior

• Default visibility: private unless the user explicitly asks for public.
• Use a simple repo name matching the user's wording when possible, normalized to GitHub style, e.g. “iOS translator” → ios-translator.
• If the repo name exists, choose the closest available variant only if the user gave broad wording; otherwise ask.
• Set a repo-local git identity if global user.name / user.email are missing.
• Verify the pushed remote before reporting success.

First-Push Workflow

1. Confirm project and GitHub auth

cd /path/to/project
git --version
gh auth status
GH_USER=$(gh api user --jq .login)
gh api user --jq .id

1. Check whether the target repo exists

gh repo view "$GH_USER/REPO" --json nameWithOwner,url,visibility 2>&1 || true

1. Create or tighten .gitignore before git add

Include at least:

# Dependencies
node_modules/
.venv/
.venv-*/

# Build outputs
dist/
dist-*/
release/
release-*/
*.tsbuildinfo

# Local caches/logs
.npm-cache/
.npm-logs/
*.log

# Xcode / Apple local state
.DerivedData/
DerivedData/
*.xcuserstate
xcuserdata/
.DS_Store

# Environment / secrets
.env
.env.*
!.env.example
*.pem
*.p8
*.p12
*.mobileprovision

1. Run a source-only secret scan

Exclude generated/dependency directories. Search for common key patterns:

• AIza — Google/Gemini keys
• sk- — OpenAI-style keys
• ghp_, github_pat_ — GitHub tokens
• hf_ — Hugging Face tokens
• -----BEGIN ... PRIVATE KEY-----