golive

Featured

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.

DevOps & Infrastructure 964 stars 66 forks Updated today MIT

Install

View on GitHub

Quality Score: 92/100

Stars 20%
99
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# 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. ## Conversatio...

Details

Author
mikehasa
Repository
mikehasa/golive-skill
Created
3 days ago
Last Updated
today
Language
TypeScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category