deploy
/deploy
Prowadzi wdrożenia aplikacji i usług na Vercel, AWS, Azure, Cloudflare, Netlify, Railway lub w kontenerach, od sekretów po wycofanie.
- Autor
- soummyaanon ↗
- Repozytorium
- engineering-os ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 08.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 08.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Prowadzi wdrożenia aplikacji i usług na Vercel, AWS, Azure, Cloudflare, Netlify, Railway lub w kontenerach, od sekretów po wycofanie.
Wyzwalacze z opisu
Oryginalny opis (EN)
Engineering OS deployment playbook — ship apps and services to Vercel, AWS, Azure, Cloudflare, Firebase, Netlify, Railway or containers: choosing a platform, environment variables and secrets, CI/CD with GitHub Actions, infrastructure as code (CDK, Bicep, Terraform), database migrations during deploys, custom domains, preview environments, rollbacks, and post-deploy verification. Use whenever the user wants to deploy, host, ship, go live, set up CI/CD, move to AWS or Azure, fix a failing deploy, or asks where to host something, even if they never say 'deploy'.
Jak działa
- 1. Pick the platform (only if it isn't already decided)
- 2. Pre-deploy checklist
- 3. CI/CD
- 4. Deploy
- 5. Verify (required before saying "deployed")
Podgląd SKILL.md
--- name: deploy description: "Engineering OS deployment playbook — ship apps and services to Vercel, AWS, Azure, Cloudflare, Firebase, Netlify, Railway or containers: choosing a platform, environment variables and secrets, CI/CD with GitHub Actions, infrastructure as code (CDK, Bicep, Terraform), database migrations during deploys, custom domains, preview environments, rollbacks, and post-deploy verification. Use whenever the user wants to deploy, host, ship, go live, set up CI/CD, move to AWS or Azure, fix a failing deploy, or asks where to host something, even if they never say 'deploy'." --- # /eos:deploy — ship it safely Deploys fail in predictable ways: a missing env var, a migration that ran in the wrong order, no way back when it breaks. This playbook makes every deploy boring: chosen deliberately, checked before, verified after, and reversible. Deploys and infra changes are outward-facing. The bash guard asks before `--prod`, `terraform apply`, `kubectl apply` and friends, and you should confirm the target with the user before the first production deploy of a project. ## 1. Pick the platform (only if it isn't already decided) Check first: `vercel.json`, `.vercel/`, `wrangler.toml`, `firebase.json`, `netlify.toml`, `railway.json`, `cdk.json`, `azure.yaml`, `*.bicep`, `*.tf`, `Dockerfile`, `.github/workflows/`. If the project already deploys somewhere, stay there unless asked. | Situation | Default | Skill | |---|---|---| | Next.js / React / static frontend, fast previews | **Vercel** | `deploy-to-vercel`; `vercel-optimize` for cost/perf; `vercel-cli-with-tokens` for CI | | Edge APIs, global low latency, cheap | **Cloudflare Workers** | `workers-best-practices` | | Full control, enterprise, existing AWS account | **AWS** | `aws-cdk` (infrastructure as code), `aws-deployment` (CodePipeline/CodeBuild CI/CD); `aws-serverless`, `aws-containers`, `aws-iam`, `aws-amplify` on demand; `architect-for-startups` for a first design | | Microsoft shop, Entra ID, existing Azure subscription | **Azure** | `azure-prepare` → `azure-validate` → `azure-deploy` (Azure Developer CLI / azd workflow); `python-appservice-deploy` for code-only Python deploys; `azure-diagnostics` when it breaks | | Simple container or long-running service, minimal ops | **Railway** / Render / Fly | `use-railway` | | Firebase / mobile backend | **Firebase** | `firebase-hosting-basics` | | Static site with forms/functions | **Netlify** | `netlify-deploy` | | Multi-cloud or existing Terraform | **Terraform** | `terraform-style-guide` | On-demand skills come with `eos enable deploy`. Building the image itself: `multi-stage-dockerfile`. ## 2. Pre-deploy checklist - [ ] **Build passes locally** with production settings (`NODE_ENV=production`, `next build`, etc.). - [ ] **Env vars**: every variable the app reads exists in the target environment (diff `.env.example` against the platform's settings). Secrets live in the platform's secret store, never in the repo or the workflow file. - [ ] **Database migrations**: backwards-compatible with the code currently running (expand → deploy → contract). Decide whether they run before the deploy (release step) or after; never in two places. - [ ] **Health check** endpoint exists and is wired to the platform. - [ ] **Rollback path** known: previous deployment promote (Vercel), previous task definition / CDK stack version (AWS), deployment slot swap (Azure), `wrangler rollback` (Cloudflare). - [ ] **Preview first**: deploy to a preview/staging environment and smoke-test it before production. - [ ] **Domains and TLS**: DNS records and certificates planned; expect propagation time. - [ ] **Cost**: rough monthly estimate for anything that scales with traffic (AWS/Azure especially). ## 3. CI/CD Use GitHub Actions unless the project has another CI (`github-actions-templates`). Minimum pipeline: install → lint/typecheck → test → build → deploy preview on PRs → deploy production on `main` with a manual approval for the first few releases. Use OIDC federation (AWS/Azure) or scoped tokens, never long-lived admin keys. Pin action versions. ## 4. Deploy Run the platform's CLI or pipeline. Watch the logs while it rolls out rather than walking away. ## 5. Verify (required before saying "deployed") 1. Open the live URL and exercise the main path once (use `agent-browser` or the `playwright` plugin for a screenshot). 2. Hit the health endpoint and one real API route. 3. Check logs and error tracking for new errors in the first few minutes. 4. Confirm the version/commit that's live matches what you meant to ship. 5. Report: URL, commit, what was verified, and the rollback command. If something is broken, roll back first, then debug (`superpowers:systematic-debugging`, `azure-diagnostics`, AWS logs).
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · soummyaanon/engineering-os | 100 | MIT |
| zeitlos/lucity | 100 | AGPL-3.0 |
| jeremylongshore/tons-of-skills-marketplace | 100 | MIT |
| zeitlos/lucity | 100 | AGPL-3.0 |
| microsoft/power-platform-skills | 100 | MIT |
| friendlyinternet/nuxt-crouton | 100 | MIT |
| wraith-proxy/wraith-skills | 100 | MIT |
| jikig-ai/soleur | 100 | Apache-2.0 |
| curiositech/windags-skills | 100 | Apache-2.0 |
Migawka bazy z 13.11.2026 · wersja paczki 836d6d51aa0c (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100deploy-setup
Konfiguruje wdrożenie na wybranym hostingu: pliki konfiguracyjne, środowiska, inwentarz zmiennych, domeny, migracje i instrukcję cofnięcia. - 95memstack-deployment-railway-deploy
Wdraża aplikacje Node.js, Python lub Docker na Railway, ze zmiennymi środowiskowymi i monitoringiem. - 100cloudflare-deploy
Wdraża aplikacje i infrastrukturę na Cloudflare z użyciem Workers, Pages i powiązanych usług platformy. - 100clerk-deploy-integration
Konfiguruje Clerk do wdrożenia na Vercel, Netlify, Railway i innych platformach oraz w środowisku produkcyjnym. - 100clerk-deploy-integration
Konfiguruje Clerk do wdrożenia na Vercel, Netlify, Railway i innych platformach oraz w środowisku produkcyjnym. - 100railway-deploy
Wdraża i zarządza aplikacjami na Railway przez CLI: konfiguracja projektu, deploye, usługi, bazy danych, zmienne, logi, skalowanie i środowiska.