Ship to Production
Build, deploy and keep it running. The path from a working branch to a service you can sleep through: reproducible container images, CI that is fast and locked down, infrastructure as code, Kubernetes manifests with sane probes and limits, progressive delivery, and the alerts and incident habits that follow a launch.
What's inside
Best for: Developers who own their deploys. Start with dockerfile-best-practices and github-actions-workflows. Each skill loads when a request matches its description, or call one directly with its $name.
- Dockerfile Best Practices Small, cached, non-root images that stop on SIGTERM
- GitHub Actions Workflows Fast PR signal, shared pipelines, guarded deploys
- GitHub Actions Security Read-only tokens, SHA pins, no injected titles
- Terraform Modules Small typed interfaces, refactors with zero destroys
- Kubernetes Manifests Deployments that survive rollouts and node drains
- Deployment Strategies Ship to 5% first, roll back in a minute
- Secrets Management No plaintext keys, rotation you have rehearsed
- OpenTelemetry One connected trace per request, vendor-neutral
- SLOs and Error Budgets Targets users feel, alerts on burn rate
- Incident Command One commander, clear roles, updates on the clock