githits-onboarding

Use this skill when the user wants to start using GitHits from their agent. This is a new-user onboarding skill: assume the user wants to create or connect a GitHits account and configure GitHits unless they explicitly say otherwise.

Current Boundary

• GitHits account sign-in/signup currently uses browser OAuth. You can start and monitor the flow, but the user may need to approve GitHits in a browser tab.
• Do not promise browserless account creation or that everything happens inside chat.
• Never ask the user to paste passwords, OAuth codes, cookies, access tokens, refresh tokens, or API keys into chat.

Command Style

• Use npx -y githits@latest ... for every normal onboarding command. This guarantees the latest published GitHits CLI behavior for new users.
• Do not use a globally installed githits binary for onboarding unless the user explicitly asks to test a local, dev, or pinned CLI build.
• If the user explicitly asks for local/dev/pinned testing, preserve the command and environment they provide.
• For explicit development testing, GITHITS_ENV=dev selects CLI/local MCP service defaults and a separate login namespace; use the same environment for login and verification. Unset or prod uses production. URL overrides remain independent; use GITHITS_CODE_NAV_URL instead of the removed PKGSEER_URL. This selector does not reconfigure hosted MCP connections or plugin endpoints.
• Prefer --json for staged init commands because agents need stable fields.
• Do not start npx -y githits@latest as a background task. If npx fails because of network, DNS, or package-fetch errors, stop and report that GitHits CLI is unavailable.