/all-deploy

Takes any website, app, API or agent from "it runs on my laptop" to "it's live on the internet" — and refuses to skip the safety audit on the way.

🌐 tododeia.com · 📸 @soyenriquerocha · 📦 Latest release

English · Español

---

---

English

The problem

Deploying is rarely hard because the commands are hard. It's hard because the commands are different every time, and because the expensive mistakes — a committed .env, a service bound to 127.0.0.1, a production push that was never checked — happen in the gap between "it works locally" and "it's live."

/all-deploy closes that gap. It reads your project, blocks on the things that actually break deploys, picks the host that fits, and only promotes to production after a preview URL has answered with a real HTTP status.

And it covers plain web pages, not just apps. If you have a folder with index.html in it and no idea where to put it, that's a first-class path: no git repo required, four free hosts with their real limits and licence terms laid out, and a set of checks aimed squarely at the things that break a page after it goes live. There's also a companion skill for that case with no terminal at all.

What it does

One command inside Claude Code walks the same path, phases 0 through 6, every time:

Phase	What happens
0 · Class + prerequisites	Decides first whether this is an app or a static site — a folder of HTML is neither Node nor Python, and used to get bounced for it. Apps need a git repo and a remote; a static site needs neither.
1 · Detect	Fingerprints your framework, runtime version, start command, port binding, database dependencies, and any existing deploy config.
2 · Audit	Runs a deterministic script over the project. Any critical finding halts the run — including in full-auto mode. Warnings print but don't block.
3 · Target	Ranks the hosts that fit your project shape and explains why. You pick, or accept the top choice.
3.5 · CLI check	Verifies the chosen target's CLI is installed and authenticated. If not, it stops and hands you the command — ! vercel login — then resumes here when you're done.
4 · Preview	Delivers your env vars to the target, then deploys to preview/staging. Never --prod on this pass.
4.5 · Health check	curls the preview URL. A 2xx or 3xx promotes. Anything else — including a connection failure — stops the run and prints the log command.
5 · Production	Prints a summary, then promotes. Full-auto gives you a real 5-second ESC window; step-by-step requires an explicit "yes".
6 · Handover	Verifies prod, confirms env vars landed, and hands you the rollback and log-tail commands for your specific target.