all-deploy
SolidDeploys any web app, API, or agent to the internet with a strict pre-deploy audit and a preview → health-check → prod flow. Detects Next, Vite, Astro, Remix, Nuxt, SvelteKit, FastAPI, Flask, Express, MCP server, Claude Agent SDK script, Python worker, Dockerized, and static projects; routes to Vercel, Railway, Docker+SSH VPS, or cloudflared tunnel. Also supports a first-class "run locally" mode. At the start of each cloud deploy the skill asks the user whether to run full-auto (audit → preview → prod in one sequence) or step-by-step (confirm each phase); the user can skip that question by saying "auto" or "step by step" up front. Use when the user says "/all-deploy", "/deploy", "/despliega", "deploy this", "ship this", "push to prod", "get this online", "deploy my agent", "deploy my FastAPI", "run it locally", "corre esto localmente", "deploy auto", "deploy step by step", "paso a paso", "how do I put this on the internet", or otherwise asks to publish a project to a URL or run it locally.
Install
Quality Score: 82/100
Skill Content
Details
- Author
- Hainrixz
- Repository
- Hainrixz/all-deploy
- Created
- 3 months ago
- Last Updated
- 1 weeks ago
- Language
- Python
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
deploy
Deploy a managed project to production, executed strictly from that project's structured deploy playbook — confirm-gated, never improvised. Use when the user says "deploy", "deploy <project>", "ship <project> to prod", "run the deploy", or "push <project> live". Reads the project's context.md + the deploy playbook it points to (e.g. a repo README "Deploy" section), presents the full ordered plan, then runs it one step at a time, pausing before each production-mutating step.
deploy
Deploy application to target platform. Use when user explicitly says 'deploy', 'push to production', 'ship it'. Handles Vercel, Netlify, AWS, GCP, DigitalOcean, and VPS with pre-deploy verification and health checks. Enforces cost allocation tags + Managed-vs-Self-Host crossover decisions so deploy choices map to actual unit economics, not hand-waved 'we'll optimize later'.
deploy
Deployment strategy, production-readiness gating, and rollback planning for AWS/EKS services. Use when user says 'how should I deploy this', 'blue-green or canary', 'are we ready to ship', 'production readiness', 'plan a rollback', 'pre-deploy check', or before a first production release. Pairs with /k8s, /ci, /github-actions, /tf which own the per-artifact checks.