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