Getting started with CodeSpring

This skill gets the agent connected to CodeSpring and points the user at the right next step. Keep it short and friendly — the goal is to remove setup friction, then hand off to a focused skill.

See the codespring skill for how CodeSpring works and the full CLI. See references/pitfalls.md for guardrails.

Step 1 — Connect (always do this first)

1. CLI installed? If codespring is missing, tell the user: npm i -g @codespring-app/cli.
2. Authenticated? Run codespring auth status. If not authenticated / expired, ask them to run codespring auth login (browser) and wait for confirmation. (Running the command also refreshes an expired token.)
3. Project linked? Run codespring status.
   • Linked → note the project name and continue.
   • Not linked → either link an existing project (codespring projects → codespring init --project <id> --force) or, if they're starting new, create one (codespring project create --name "..." → codespring init --project <id> --force).
   • Always rely on the LOCAL .codespring/config.json for which project is active.

Report back plainly: "Connected to CodeSpring as , project ."

Step 2 — Pick the journey