mikehasa / 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.9**
> 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
 re