golive-skill

GoLive

English · 简体中文 · 日本語 · 한국어 · Español · Português (Brasil) · Deutsch

Take your agent-built product live: hosting, database, auth, domain, email, payments — on your own accounts. Then hand it over, or tear it all down.

Your coding agent can build an app in minutes. Getting it to real users still means accounts, hosting, databases, domains, secrets and connected services. GoLive is the open-source Agent Skill for that work: it detects what your app needs, plans the exact changes, asks for your approval, applies them with your own logins, and verifies what actually works — then records what it created, re-checks it for drift on demand, and can remove it again.

Automate the parts providers expose. Guide you through the parts that need a human. Verify what can be observed, and make unfinished work clear. No GoLive account, hosted backend or product telemetry.

Early alpha · 0.1.0-alpha.8 Disposable live tests now cover six journeys: hosting (Vercel, Netlify), database (Supabase, Neon), custom-domain DNS (Porkbun, GoDaddy), transactional email (Resend), test-mode payments (Stripe) and Supabase authentication, plus the teardown uninstall path. The ownership document and the on-demand golive status drift check are implemented with test coverage (golive status also ran read-only in a live validation), while the broader roadmap is our direction, not a claim that it is all built.

Before you hand over production access

Whether to give an agent your provider accounts comes down to four questions. These are this project's answers, with the limits stated where they exist.

• You still approve every write. Nothing reaches a real account without a plan you have seen and approved: apply refuses without that plan's id and --yes, and it re-checks the plan's identity before writing, so a changed release or config invalidates the old approval. DNS writes need --confirm-dns, deletions need --confirm-destroy, and live-mode steps — live payments, production data, a real account — need --confirm-live, which now includes a project's first production deploy, because approving a plan alone used to be enough to write production for the first time. Credential values are read only in-process, never printed, and never in arguments, plans, state or reports; the file golive stores them in is plaintext at mode 0600 outside your repo, not a keychain. One limit worth naming: those flags are arguments the agent passes on your behalf, and an agent already logged in to your provider can write there with no golive plan at all. Trust, access and control separates what the code enforces from what is only an instruction the agent is asked to follow.
• A run stops rather than pushing on. apply stops at the first failed check, missing confirmation, missing prerequisite or provider that contradicts the plan. Later steps do not run, and the next apply resumes at that step. Recovery covers reading the failure, which steps resume, and the cases that need a reviewed decision first.
• Rollback is narrow, opt-in and never automatic. A failed check never triggers a rollback. release.rollback: true plans one step that re-points production at an earlier deployment golive itself recorded; a deployment built by a dashboard, a Git push or a pull request is not a target, and it touches no data, DNS, payment or email resource. Only Netlify supports these re-points today — on Vercel you correct production in the dashboard (Vercel's adapter has no read of what production serves). Promotion and rollback are implemented and mock-covered, not live-validated.
• Nothing is left behind silently — which is not the same as nothing being left behind. golive teardown removes only resources it can prove it created, re-reads the DNS zone and the host project after deleting, and names every leftover it cannot remove — Supabase and Neon projects, the Resend sending domain, a zone or host project it cannot read — as a handoff saying what remains and how to remove it by hand. A removal also forgets the baseline golive recorded for that resource, so golive status does not report golive's own teardown as drift.

Those answers in full: trust, access and control and recovery. The architecture is the product contract, provider scope says what each provider can do today, the validation record separates what has been exercised live from what is only mock-covered, and distribution covers installation and updates.

Install · Use GoLive · See the workflow · Alpha scope · Roadmap · Contribute

Install

You need Node.js 20+, npm/npx, Git, and a coding agent that can load skills and run commands. Installation has been checked for Codex and Claude Code; other clients are unverified.

Install once for all your projects. Run this from any directory:

npx skills add https://github.com/mikehasa/golive-skill --skill golive --global

Select your agent when prompted: use the arrow keys to move, Space to select, and Enter to confirm. That screen is waiting for input; installation continues after you confirm.

To skip the agent picker, use the command for your agent:

# Codex
npx skills add https://github.com/mikehasa/golive-skill --skill golive --global --agent codex --yes

# Claude Code
npx skills add https://github.com/mikehasa/golive-skill --skill golive --global --agent claude-code --yes

For installation in just one project, run from that project's repository and omit --global.

Or paste this into your coding agent:

Install the GoLive skill globally so I can use it across projects:
npx skills add https://github.com/mikehasa/golive-skill --skill golive --global

Target the agent I'm using: add --agent codex --yes for Codex, or
--agent claude-code --yes for Claude Code. Keep --global.
If the agent isn't clear, ask me which one.

Verify the installation with:
node <installed-skill-dir>/scripts/golive.mjs version --json
Tell me if I need to reload skills or start a new session.
Stop after installation; don't connect accounts or deploy yet.

The install includes the instructions, provider references and prebuilt runtime. It does not connect accounts or deploy anything. See installation and updates for noninteractive agent flags, runtime verification and the optional own installer.

Install from npm

The same skill is published to npm as golive@0.1.0-alpha.8 (dist-tags alpha and latest), which installs it offline, with no Git or Skills CLI involved:

# Codex
npx golive@alpha install --agent codex

# Claude Code
npx golive@alpha install --agent claude

Add --global to install into your home directory (~/.agents/skills/golive or ~/.claude/skills/golive) instead of the current project; --agent claude-code, the spelling the Skills CLI channel uses, is accepted as well. The installer copies the complete skill the package ships with, refuses an existing destination, and never connects provider accounts.

Both channels carry the same release. The npm package publishes the version in this repository, including the standalone installer helpers, so an npm installation is an owned copy that updates in place. The earlier 0.1.0-alpha.0 snapshot has no updater: remove that copy and reinstall, or use the GitHub channel, which manages its own installs. The npm package also exposes the terminal CLI: the golive commands npx golive@alpha help, version, update-check, credentials, detect, menu, init, doctor, plan, teardown, apply, verify, status and handoff (apply needs the approved plan ID and explicit confirmation), plus the installer commands install, install-status, update, rollback, update-policy and recover-lock for the copies it owns. See installation and updates for the channel's exact limits.

Install from ClawHub (OpenClaw)

If you use OpenClaw, the same skill is listed on ClawHub, its public registry:

npx clawhub@latest install golive     # into ./skills, recorded in .clawhub/lock.json
npx clawhub@latest update golive      # later updates stay with ClawHub

ClawHub installs into the current directory's skills/ folder rather than an agent's global skills directory, so it suits an OpenClaw workspace; Codex and Claude Code are the clients this project verifies, through the two channels above. The registry keeps its own metadata (_meta.json, skill-card.md, .clawhub/) beside the bundle, which golive's own integrity check ignores. See installation and updates for the channel's limits.

Use GoLive

Open your app repository in your coding agent. After installation, reload skills or start a new session if GoLive does not appear. The skill's name is golive. For the standalone installation above, type one of these in your agent's chat:

Agent	Example prompt
Codex	$golive Help me take this app live.
Claude Code	/golive Help me take this app live.

You can also ask in plain language:

Use the golive skill to take this app live. Keep the providers it already uses.
Show me the destination accounts and plan before changing anything.

GoLive inspects the app, asks about missing providers, and presents the destination accounts and plan for your approval before making provider changes.

These are chat prompts. golive skill is not a command. Installing through npx skills add does not add a golive command to your terminal; the agent runs the included CLI from the installed skill directory. The npm package can also install the skill offline and exposes that CLI as npx golive@alpha <command>; its terminal commands run individual operations rather than the conversational skill workflow.

What a run looks like

An illustrative conversation for an app that already uses Supabase:

You: Use golive to take this app live. Use test resources for now.

Agent: This app uses Supabase. Where would you like to host it?

1. Vercel — built-in hosting workflow; live-tested with Supabase.
2. Netlify — built-in hosting workflow; the live-tested pairing is Netlify + Neon.
3. Other — tell me your provider; I'll try a guided setup using its official tools and docs.

You: Vercel.

Agent: We'll keep Supabase. Does this app already have a Supabase project, or should we create a new test project?

You: Create a new one.

Agent: Run vercel login and supabase login in a separate terminal window. I'll check which account and organization are connected when you're done.

You: Done.

Agent: Here's the plan: create a new test frontend project in your selected Vercel team, create its database in your selected Supabase organization, transfer the required environment values, and deploy. I'll show the actual destination names and IDs, resource settings and cost information with the plan. Approve before I apply it.

You: Approved.

Agent: The deployment is live. Here is the URL, the verification report, and anything still