all-deploy skill
The all-deploy skill puts a site, app or API online: audit, preview, response check and rollback
- 74 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Runs hosting CLIs under your account and publishes the project to the public internet, and production gets code after the preview check
- Passes environment variables to the chosen host and reads project files including `.env` during the secrets audit
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/all-deployDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Runs hosting CLIs under your account and publishes the project to the public internet, and production gets code after the preview check
- Passes environment variables to the chosen host and reads project files including `.env` during the secrets audit
This is third-party code. Review the repository files before installing.
What it does
The `/all-deploy` command in Claude Code walks the same path from phase 0 to 6. First the skill decides the project class: an app or a static site that needs neither git nor a runtime. Then it identifies the framework, runtime version, start command, port and databases. The audit phase runs a deterministic script: any critical finding halts the deploy, even in full-auto mode. Critical findings are secrets in tracked files including a committed `.env`, a missing `.gitignore`, a missing Node lockfile, an incomplete `.env.example`, a dirty working tree, no git remote and critical dependency vulnerabilities from `npm audit` and `pip-audit`. Warnings such as localhost-only binding or an unpinned runtime print but do not block. Fixes are shown as a diff before writing. The skill then ranks fitting hosts, among them Vercel, Netlify, Railway, Render, Cloudflare Pages, GitHub Pages and Docker on a VPS, checks that the target CLI is installed and signed in, deploys a preview, calls `curl` on its address and moves to production only after a 2xx or 3xx answer. In auto mode a five-second ESC window precedes production, and step mode needs an explicit yes. At the end the skill hands over rollback and log commands for the chosen host. Modes: `/all-deploy auto`, `/all-deploy step`, `/all-deploy local`.
Who it is for. Developers and first-time site builders working with an agent who need a reliable route to a public address without relearning each host's commands.
Good fit when
- The project runs on a laptop and you need it online with a prior check of secrets and lockfiles
- You have a folder with `index.html` and no git: a static site must go to a free host
- A deploy succeeds but the service serves nothing because of binding to 127.0.0.1, and that error should be caught before production
- After the deploy you need rollback and log commands for the chosen host
Not a fit when
- You need complex Kubernetes orchestration or infrastructure as code: the skill targets ready hosts and Docker on a VPS
- The deploy must run without the host CLI and sign-in: the skill stops and asks you to log in
- Git history already holds a leaked secret: the skill suggests `trufflehog` but does not rewrite history
Example request
Deploy this project to the internet step by step: check secrets, show ranked hosts, make a preview and only then productionLimitations
- The host CLI and sign-in are required before deploy, and the skill stops and asks you to run, for example, `! vercel login`.
- Apps need a git repository and remote, static sites do not. The Docker on a VPS flow needs no remote.
- The skill neither scans nor rewrites git history: it prints the command `trufflehog git file://.` and leaves the decision to you.
- In auto mode a 5-second ESC window precedes production, so watch the deploy.
How to disable. Delete the skill folder with rm -rf ~/.claude/skills/all-deploy or your own skill manager. The skill installs nothing outside that folder. Projects it deployed stay on their hosts and are removed in the host dashboard or CLI.
FAQ
How do I install all-deploy?
Run `git clone https://github.com/Hainrixz/all-deploy.git ~/.claude/skills/all-deploy`. After that `/all-deploy` works in Claude Code. Updating is `git pull` in the skill folder.
What stops a deploy?
Critical audit findings: secrets in tracked files, no `.gitignore`, no Node lockfile, an incomplete `.env.example`, a dirty tree, no remote and serious dependency vulnerabilities. The stop works in auto mode too.
Which hosts are supported?
Named targets include Vercel, Netlify, Railway, Render, Cloudflare Pages, GitHub Pages and Docker on a VPS, and static pages get four free hosts with limits and license terms laid out. The skill ranks options by project shape.
Do I need git for a static site?
No. A folder with `index.html` takes a separate path with no git repository or remote: the skill checks the page, compares free hosts and publishes. Apps need git and a remote.
What are the auto and step modes?
In `/all-deploy auto` the skill goes from audit to production with a five-second ESC window before production. In `/all-deploy step` it stops for your approval between audit, preview and production.
Discussion
No questions or reviews yet.
Related
SkillsThe $cv-deploy skill helps an agent set up a computer-vision host: drivers, OpenCV and FFmpeg builds, RTSP streams and services
A Claude Code skill that rolls out AEnvironment platform environments as temporary instances or permanent services
A skill set for website performance and scalability, currently holding ooda-loop: observe, orient, decide, act.
31 DevOps skills for Claude Code and Codex: config generators, validators and a Kubernetes debugger for Terraform, Helm, CI and Docker
A skill and a Go binary: with your approval the agent installs apps from a 93-app catalog on your home server via Docker Compose
A small server and the skb CLI for private skill distribution: publish, version, install and roll back skills across agents
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| all-deploy (this card) | no | 74 | |
| Ship Safe | no | 872 | checks a project before release and does not deploy to hosts |
| release-it | no | 9,083 | ships version releases with no host choice or preview response check |
README in short
The README states the goal: take any site, app, API or agent from a local run to a public address and never skip the security audit. A table describes phases 0 to 6, and install comes down to a single clone. Modes and trigger phrases in English and Spanish follow, then a detailed list of critical and non-critical audit findings and a separate branch for static sites with its own checks. A table of targets with their rollback story closes the page.