# Golive

Take an agent-written app from repo to live production on the user's OWN accounts, with...

- Repository: https://github.com/mikehasa/golive-skill (1353 stars)
- Category: Data and ML
- License: MIT
- Last updated: 2026-10-11
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add mikehasa/golive-skill --skill golive -g -a claude-code -y`
Codex: `npx skills add mikehasa/golive-skill --skill golive -g -a codex -y`
Cursor: `npx skills add mikehasa/golive-skill --skill golive -g -a cursor -y`
Gemini CLI: `npx skills add mikehasa/golive-skill --skill golive -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add mikehasa/golive-skill`

## Description

Take an agent-written app from repo to live production on the user's OWN accounts, with providers they choose (hosting, database, auth, payments, email, domain/DNS). The human connects accounts and approves changes; supported wiring operations run through a local CLI and produce verification evidence with explicit limits. Use when the user wants to ship, deploy, go live, launch, publish, or put their app online, or asks to wire up env vars, webhooks, auth settings (signup, email confirmation, password policy), a real signup → confirmation email → login journey, password recovery, account isolation between two users, auth redirects, email DNS or a custom domain.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# golive: ship this app to production, on the user's own accounts

Help the agent take an app live on accounts the human owns. The `golive` script handles supported
provider operations after approval and records what its checks establish. The human connects
accounts and handles purchases; app migrations, business flows and guided steps need their own
review. Never turn an infrastructure check into a claim that the entire app works.

```bash
node <this-skill-dir>/scripts/golive.mjs <command> --json
```

`<this-skill-dir>` is the folder containing this SKILL.md. Every command prints one JSON document.
Exit code `2` means "worked, but something needs attention": read the JSON.

## Start with a verified release

At the start of a new deployment run, run `version --json` and `update-check --json` using the
script above. The runtime verifies the complete instruction/reference/script bundle before
accessing accounts. Update checking reads only public metadata, is cached and bounded, and an
offline/unavailable result does not block the deployment flow. `GOLIVE_UPDATE_CHECK=0` disables it.
Read `references/updates.md` for installation ownership, explicit updates, rollback and opt-in
automatic replacement. Automatic replacement is off by default and only runs between deployment
runs for copies owned by our installer. Skills CLI and plugin copies stay with their managers.
Never update between a plan and its apply. A changed release requires a new plan and human approval.

## Conversation and progress

The rest: https://github.com/mikehasa/golive-skill/blob/HEAD/skills/golive/SKILL.md