explaingit

sac-y/go-live

13Audience · vibe coderComplexity · 1/5ActiveLicenseSetup · easy

TLDR

A Codex Skill for mobile users that auto-deploys every code change to a public URL using whatever the project already has, since localhost is unreachable from a phone.

Mindmap

mindmap
  root((go-live))
    Inputs
      Code change request
      Project deploy config
    Outputs
      Public preview URL
      Verification result
      Change summary
    Use Cases
      Mobile Codex preview
      One-tap deploy
      Iterate on a phone
    Tech Stack
      Skill
      Codex
      Vercel
      Netlify
      Cloudflare

Things people build with this

USE CASE 1

Preview a project on your phone by asking Codex to deploy after each change

USE CASE 2

Skip localhost setup when coding from the ChatGPT mobile app

USE CASE 3

Auto-publish a static site to its existing Vercel or Netlify hookup after each Codex edit

Tech stack

SkillCodexVercelNetlifyCloudflare

Getting it running

Difficulty · easy Time to first run · 5min

Needs a project already wired to a deploy target (Vercel, Netlify, Cloudflare, Firebase, or Pages) for the auto-deploy step to find anywhere to push.

MIT license, free to use, modify, and redistribute with attribution.

In plain English

Go Live is a small extension, called a Skill, for the Codex coding assistant. It is written for people who use Codex on their phone, where the usual local development server at localhost is not reachable. The README is mainly in Chinese with an English version linked beside it. The pitch is short: after every code change, Go Live should push the project to a public URL so the user can open it from their phone and actually see the result. Installing it works in two ways. From a desktop command line, you run npx skills add Sac-Y/go-live, which uses the skills.sh ecosystem to register the Skill with Codex. Inside the Codex app or ChatGPT mobile app, you ask Codex in plain language to install the Skill and paste the GitHub URL. After that, you talk to Codex normally and ask for a phone preview, and the Skill takes care of the deploy step. The README describes the Skill's behavior as a fixed loop. First it makes the code or content change you asked for. Then it runs the fastest meaningful check in the project, such as build, lint, typecheck, or a smoke test. Then it deploys using whatever the project already has set up, with a preference for existing Vercel, Netlify, Cloudflare, Firebase, GitHub Pages, or the project's own CI and CD pipeline. After the deploy it opens the public URL to confirm the page loads and shows the change, and only then replies with the link, a summary of what changed, and the verification result. The README is explicit that the Skill is not tied to any single host. It will prefer the deploy method the project already uses rather than introducing a new one. If the project does need a platform plugin or login, such as Vercel, Cloudflare, or GitHub, Codex will ask for permission at the point it is needed rather than up front. The author lists a few rules. The Skill should not return a localhost link unless the user explicitly asked for one. It should not switch deploy targets midway if the project is already wired to one. If the deploy needs a login, project binding, environment variable, or a commit and push step, Codex should call out the blocker rather than silently fail. And it should not claim the deploy succeeded until the public URL has actually been checked. The project is MIT licensed.

Copy-paste prompts

Prompt 1
Install the Sac-Y/go-live Skill into my Codex CLI via npx skills add
Prompt 2
After this edit, run my project's build then deploy to my existing Vercel project and return the public URL
Prompt 3
Configure go-live to prefer Cloudflare Pages over Vercel for this repo
Prompt 4
Make a phone preview of the current branch and confirm the page loads before replying with the link
Open on GitHub → Explain another repo

Generated 2026-05-22 · Model: sonnet-4-6 · Verify against the repo before relying on details.