mikehasa/golive-skill / skills/golive
golive
FlaggedTake 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.
| File | Kind | Size |
|---|---|---|
| LICENSE | other | 1.0 KB |
| SKILL.md | skill md | 50.0 KB |
| THIRD_PARTY_NOTICES.md | markdown | 817 B |
| references/cloudflare-dns.md | markdown | 7.9 KB |
| references/godaddy.md | markdown | 3.9 KB |
| references/guided.md | markdown | 9.2 KB |
| references/neon.md | markdown | 4.4 KB |
| references/netlify.md | markdown | 6.9 KB |
| references/plan-and-verify.md | markdown | 47.4 KB |
| references/porkbun.md | markdown | 3.4 KB |
| references/posthog.md | markdown | 10.2 KB |
| references/resend.md | markdown | 8.6 KB |
| references/sentry.md | markdown | 10.7 KB |
| references/stripe.md | markdown | 13.1 KB |
| references/supabase.md | markdown | 49.7 KB |
| references/troubleshooting.md | markdown | 5.2 KB |
| references/updates.md | markdown | 5.0 KB |
| references/uptimerobot.md | markdown | 12.3 KB |
| references/vercel.md | markdown | 13.2 KB |
| release.json | config | 2.4 KB |
| scripts/golive.mjs | script | 1.2 MB |
| scripts/install-cli.mjs | script | 5.0 KB |
| scripts/install-lib.mjs | script | 24.4 KB |
references/updates.md
View on GitHub# Release integrity, installation ownership and updates
Run `node <this-skill-dir>/scripts/golive.mjs version --json` when starting a new deployment run.
It verifies the complete skill against `release.json`, including instructions, references and
runtime. A missing/mixed/corrupt bundle stops before account access. Repair it using the same
installation manager; do not download just a replacement script.
Then run `node <this-skill-dir>/scripts/golive.mjs update-check --json`. This reads only public
release metadata, uses a 24-hour cache and a bounded timeout, and never reads project credentials.
An unavailable/offline result does not block deployment commands. Set `GOLIVE_UPDATE_CHECK=0` or
pass `--offline` to skip the network check. Explain current/latest versions only when useful;
do not repeatedly announce an unchanged result.
## One manager per installed copy
- Skills CLI owns installations it made. Use `npx skills update golive -p` for project scope or
`-g` for global scope, between runs. A pinned source stays pinned until explicitly changed.
- Plugins use their plugin manager. Never edit plugin caches or lockfiles directly.
- Manual copies are replaced as a complete verified bundle by the user.
- The optional own installer manages only its own receipt-backed copies. Run
`node <this-skill-dir>/scripts/install-cli.mjs install-status --json` to inspect one. It reports
duplicates without deleting them. An external copy is never adopted or overwritten implicitly.
## Own installer commands
At a new run boundary, an owned installation can explicitly update to an immutable public tag:
```bash
node <this-skill-dir>/scripts/install-cli.mjs update --between-runs --ref v<version> --json
node <this-skill-dir>/scripts/install-cli.mjs rollback --json
node <this-skill-dir>/scripts/install-cli.mjs update-policy --auto on --json
node <this-skill-dir>/scripts/install-cli.mjs update-policy --auto off --json
```
Automatic replacement is off by default. Only after the user opts in, when `update-check` reports
`manager: owned`, `automaticInstall: true`, `status: available` and a valid `latest.source.ref`,
the agent may invoke `update --auto --between-runs --ref <that-exact-tag> --json` at the start of a
new run. Reload the entire skill and verify its new version afterward. This is startup-driven
automation, not a background daemon. Pinned copies never auto-update.
Updates stage the complete bundle, verify every file and run offline smoke checks — `help` and
`menu --json` under a guard that denies the common network and subprocess entry points, including
socket prototypes, DNS, dgram, HTTP/2, worker threads and cluster forks — before switching the active
pointer. That guard is a sanity check for a broken or careless release, **not a sandbox**: it does not
contain a deliberately hostile bundle, and the gate that matters is the human approving one explicit
update to an immutable public tag. The previous version is retained for local rollback. A
failed/stopped update keeps the prior active version; a stale lock requires the explicit
`recover-lock` command after confirming the original process has stopped. Never remove installation
metadata by hand to bypass a refusal. These operations do not change app config/state, credentials or
cloud resources.
Rolling back the skill does not roll back a deployment or database.
## Approval and resume boundary
Never install an update between `plan` → human approval → `apply`. Plans bind the verified release
and schema versions. After any bundle change, discard the old approval, re-observe with `plan`,
show the new plan and obtain a fresh approval. No old runtime is fetched to make approval pass.
Compatible state keeps resource IDs, fingerprints and evidence. Identical completed operations
remain completed. Changed, failed or ambiguous historical writes may require reconciliation;
do not delete state or force replays to get past that guard. Two exemptions resume by themselves,
because the step declares it: teardown's destruction steps (a deletion re-checks ownership and is
idempotent) and any step whose risk declares `risk.replayable` (an idempotent write that re-observes
the provider and golive's own recorded resource before acting, e.g. the auth test account's password
rotation). Everything else stays blocked. Incompatible schemas stop safely.
There is no general reconciliation command yet. Explain the blocked operation and prepare a
separately reviewed recovery after inspecting the provider; do not promise automatic recovery.
`golive status` states the same boundary: a step that failed under another (or an unknown) release
appears as `release:step:<id>` with `action: human` when it declares neither exemption, and the item
says there that re-running `apply` cannot succeed until that reconciliation has happened — including
when the current plan no longer carries the step at all. A step this release recorded, or one that
declares the exemption, keeps the plain re-run advice.
Existing private golive deployments are not automatically migrated to a differently named product.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |