GoLive Launch Assistant
Let your coding agent plan and deploy an app, with your approval before it changes real cloud accounts.
- Source repo
- mikehasa/golive-skill
- Stars
- ★ 1.2k
- Last updated
- 4d ago
- License
- MIT
- Primary language
- TypeScript
- FA score
- 82/100 · Good
At a glance
- How it runs
- Works with
- Universal · cross-platformCodex · Claude Code
- Cost
- Free, no paid service needed
- Setup effort
- High · needs real infrastructure
- You'll need
- Typical use
- A developer using Codex or Claude Code who wants to deploy an existing app to Vercel or Netlify.
- Not a fit if
- Users who need a validated first-account setup
- Teams requiring live validation across all app frameworks and provider pairings
- Source review
- 82/100 · Good
What does this agent do, and when should you use it?
GoLive is an open-source Agent Skill with a zero-dependency Node.js CLI for assessing and planning an app launch from its repository. The conversational skill guides the workflow, while the CLI handles detection, planning, approved changes and verification. Built-in paths cover Vercel or Netlify hosting, Supabase or Neon databases, and live-tested DNS, Resend email, Stripe test payments and selected Supabase Auth workflows. Runs produce verification reports and resource state, with optional handover documentation; `golive status` checks recorded baselines for drift on demand. Changes go to your own provider accounts, and teardown is limited to resources GoLive can prove it created and requires separate approval.
After you install and invoke the golive skill in an app repository, the coding agent inspects the app and existing services, asks about missing providers, and presents the destination accounts and plan. CLI commands including detect, plan, apply, verify, status, handoff and teardown support detection, planning, execution, verification, drift checks, handover records and approved cleanup. apply requires a plan ID and --yes; DNS, live-mode and deletion actions require their respective additional confirmation flags. The CLI uses your signed-in provider accounts or local credentials, writes resources, and produces .golive/report.json, GOLIVE_REPORT.md and state files; golive handoff --write also creates GOLIVE_HANDOVER.md. A run stops at the first failed check or missing prerequisite and can resume from that step.
- A developer using Codex or Claude Code who wants to deploy an existing app to Vercel or Netlify.
- A team that wants to create a test database in its own Supabase or Neon account and connect it to an app.
- A maintainer attaching a custom domain to Vercel and approving DNS writes through Porkbun or GoDaddy.
- An app developer validating a Resend transactional-email setup or Stripe test-mode payment flow.
- A maintainer who needs resource ownership records, on-demand drift checks, or cleanup of temporary resources GoLive created.
How do you install or deploy this agent?
Requires Node.js 20+, npm/npx, Git, and a coding agent that can load skills and run commands. The README says installation has been checked for Codex and Claude Code; other clients are unverified. Install globally with the Skills CLI:
npx skills add https://github.com/mikehasa/golive-skill --skill golive --global --agent codex --yesFor Claude Code, replace --agent codex with --agent claude-code. The npm channel is another documented option:
npx golive@alpha install --agent codex --globalInstallation copies the skill but does not connect accounts or deploy. Omit --global to install for the current project.
How do you use this agent?
Open the target app repository in your coding agent. If GoLive does not appear, reload skills or start a new session. First invocation:
$golive Help me take this app live.In Claude Code, use /golive Help me take this app live.. Follow the prompts to sign in to required providers and review the destination accounts and plan. The npm package can also run individual CLI operations, for example:
npx golive@alpha help
npx golive@alpha detect
npx golive@alpha planTo make changes, supply the plan ID and explicit approval; DNS, production and deletion actions also need additional confirmations. Run verification afterward and inspect GOLIVE_REPORT.md; use golive handoff --write if you need the handover document.
What are this agent's strengths and limitations?
- Requires a reviewed plan before changes; writes need a plan ID and explicit approval, with extra gates for DNS, production and deletion.
- Supports Vercel/Netlify hosting and Supabase/Neon databases, with live-tested evidence for the documented paths.
- Produces inspectable verification reports, on-demand drift checks and ownership handover records; a failed step stops later steps.
- Can remove resources it can prove it created after approval, and lists resources it cannot remove as manual handover items.
- It is early alpha; first-account setup and all app frameworks are unvalidated, and some provider pairings have only mock coverage.
- Real deployments require your own cloud accounts, provider logins and infrastructure; a full launch may also involve DNS, database, email or payment services.
- Credentials are stored outside the repository in a local plaintext file with mode 0600, not an OS keychain; processes running as the same user can read it.
- Guided setup for other providers does not guarantee completion or equivalent verification, and some resources require manual removal.
How does this agent compare with similar options?
Compared with signing in to provider dashboards and configuring each service manually, GoLive connects inspection, planning, approval, execution and verification in a coding-agent workflow while leaving provider accounts in your control. For providers without built-in adapters, it offers best-effort guidance without the same completion or verification guarantees.
Key facts side by side with the most closely related agents.
| Agent | Source review | Form / cost | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|---|
| GoLive Launch Assistant This agent | 82 · Good | Agent plugin / skillFree | ★ 1.2k | 4d ago | TypeScript | Codex · Claude Code |
| TrustGraph | 62 · Some gaps | CLIFree + model costs | ★ 2.8k | 15d ago | Python | OpenAI API · Claude API |
| Kortix | 60 · Some gaps | CLIFreemium | ★ 20k | 1d ago | TypeScript | — |
| Kestra Workflow Orchestration Platform | 53 · Major gaps | Self-hosted serviceFreemium | ★ 29k | 1d ago | Java | — |
How does FollowAgents rate this agent?
Why each dimension lost points
The evidence requires a plan ID, explicit approval, and extra confirmations for DNS, destruction, and production actions. Credentials are kept out of arguments, plans, and reports, and the state file is mode 0600, but credentials are stored locally in plaintext and an Agent already logged into a provider can bypass GoLive. Tests and documentation show scoped provider permissions, secret redaction, and resource ownership gates; the supplied material does not establish that all dependency risks are addressed. External effects, stop conditions, and teardown boundaries are well described. Rollback is limited and supported only for Netlify. Publisher identity is unverified; repository attribution exists, but maintenance and update responsibility are unclear.
The documentation distinguishes implemented features, mock coverage, and live validation, and mentions defects that were fixed. The material is extensive and README.de is marked unreviewed, so consistency across versioned text cannot be established. CI configuration, Node requirements, and multiple install channels support availability, though locked dependencies and remote install channels leave supply-chain boundaries. Failure guidance is actionable; supplied tests especially cover permission, rate-limit, and safe-response handling, so this criterion scores strongly.
The product targets users deploying apps with coding Agents and covers hosting, databases, DNS, email, payments, and authentication, while describing generic provider guidance as best-effort. It clearly states Alpha provider scope, validation scope, and human steps. Triggering depends mainly on skill instructions and user prompts, so the evidence does not establish strong protection against unintended activation. Codex, Claude Code, Node 20+, and several install paths are documented; other clients are unverified, limiting environment fit.
Documentation is organized around trust, recovery, architecture, providers, validation, and distribution. Installation, updates, workflow examples, command distinctions, roadmap, and limitations are covered. The MIT license is explicit. The alpha version is present, and CI builds from the package version and checks the committed bundle; however, the supplied material does not establish a clear change history or maintenance owner, and multiple names and release channels add some user burden.
Plans, verification reports, handoff, status, and teardown help users review targets, outcomes, and remaining work. The cross-provider workflow offers clear deployment orchestration value. Alpha scope remains limited, users still handle logins, identity checks, and some follow-up tasks, and provider coverage varies, so the cost-benefit case is not complete.
The README separates specific features and validated paths from mock-covered, unvalidated, and limited areas. Validation documentation, CI configuration, and adapter tests provide complementary evidence. Test files are static evidence and cannot substitute for executed runs; corroboration across sources is not complete. The material generally distinguishes factual claims, validation claims, and their limits.
- This is a low-confidence static assessment; code was not run and the documented validation claims were not independently reproduced.
- Credentials are stored in a local plaintext file outside the repository; an Agent authenticated to a provider can bypass GoLive's plan and confirmation flow.
- The project is early Alpha. Only the listed provider combinations have live validation; other paths may have mock coverage only or best-effort guidance.
- README.de is marked unreviewed; publisher identity and maintenance responsibility are unverified or unclear.
FAQ
Do I need to pay for a GoLive service?
Can the agent change a production account without my approval?
apply requires a plan ID, --yes and any confirmation flag required for that action. However, an agent already signed in to a provider can bypass GoLive and write there directly.Which hosting and database providers are supported?
What happens if a step fails?
apply resumes at that step. Some teardown actions cannot be automated and are reported as handover tasks.Where are credentials stored?
~/.config/golive/credentials, a local plaintext file outside the repository with mode 0600, not an OS keychain. Values are kept out of plans, state, reports, command arguments and output.