mikehasa/golive-skill

What it solves

Coding agents can build an app in minutes, but getting it to real users still means accounts, hosting, databases, domains, secrets and connected services. GoLive is an 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. It then records what it created, re-checks it for drift on demand, and can remove it again. The goal is to automate the parts providers expose, guide you through the parts that need a human, verify what can be observed, and make unfinished work clear — with no GoLive account, hosted backend or product telemetry.

How it works

GoLive inspects your app, asks about missing providers, and presents the destination accounts and plan for your approval before making any provider changes. Nothing reaches a real account without a plan you have seen and approved: "apply" refuses without that plan's id and a yes flag, and it re-checks the plan's identity before writing, so a changed release or config invalidates the old approval. Runs stop at the first failed check, missing confirmation, missing prerequisite or provider contradiction, and the next "apply" resumes at that step. Rollback is narrow, opt-in and never automatic — it only re-points production at an earlier deployment golive itself recorded, and only Netlify supports this today. "golive teardown" removes only resources it can prove it created, re-reads the DNS zone and host project after deleting, and names every leftover it cannot remove as a handoff. Credential values are read only in-process, never printed, and stored in a plaintext file at mode 0600 outside your repo. The skill includes a general guided flow for providers outside the built-in list, using official CLIs, MCP integrations or APIs, with best-effort verification.

Who it's for

Developers using coding agents — installation is verified for Codex and Claude Code (requires Node.js 20+, npm/npx, Git) — who have built an app and want to take it live on their own infrastructure: hosting, database, auth, domain, email and payments, while keeping approval and control over every change. It's also for those who need to hand the finished product over or tear the test resources down cleanly afterward.

Highlights

• Live-tested paths for two hosting choices (Vercel, Netlify) and two databases (Supabase, Neon), including provisioning, environment wiring and deployment.
• Live-tested custom-domain DNS (Vercel + Porkbun, Vercel + GoDaddy) with ownership verification and HTTPS serving.
• Live-tested transactional email (Vercel + Resend) and test-mode payments (Vercel + Stripe) including a real test-card payment.
• Supabase Auth support: signup, email confirmation, password recovery, custom SMTP and account isolation, with live validation on several legs.
• You approve every write: apply requires the plan's id and explicit confirmations, with separate flags for DNS writes, destroys and live-mode steps.
• Records what it created, re-checks for drift with "golive status", and removes resources with "golive teardown" — only what it can prove it created.
• No GoLive account, hosted backend or product telemetry; credentials stay local at mode 0600.
• A general guided flow for other providers, with explicit limits and best-effort verification.

Early alpha 0.1.0-alpha.9: some features are mock-covered only, not live-validated; the roadmap describes direction, not a claim that everything is built.