← ClaudeAtlas

safe-deploylisted

Deploy a project to production with pre-flight checks, a database backup, verification, and a written rollback note.
simbaTmotsi/simba-skills · ★ 2 · DevOps & Infrastructure · score 78
Install: claude install-skill simbaTmotsi/simba-skills
# Safe deploy A production deploy for a project running on a host you can reach. Every step that changes running state needs the user's explicit go-ahead in this conversation. Touch only this project's containers and services; other stacks on the same host (shared proxies, other apps) are off limits. ## 1. Discover how this project deploys (read-only) Find the existing path before inventing one. Look at, in parallel: - `docker-compose*.yml` / `compose*.yaml`, `Dockerfile*`, `.env*` examples - deploy or manage scripts (`scripts/`, `bin/`, `Makefile`, `justfile`, `package.json` scripts) - CI and CD config (`.github/workflows/`, `.gitlab-ci.yml`), systemd units that start the stack on boot - `README`, `CLAUDE.md`, `AGENTS.md`, `docs/` for deploy notes, past incidents and "never do X" rules - the running state: `docker compose ps`, `docker ps --format '{{.Names}}\t{{.Image}}\t{{.Status}}'` Write down: which services are app services (safe to recreate) versus stateful ones (database, cache, search, proxy), how migrations run, where health endpoints live, and any scheduled jobs that must not be interrupted. If CI deploys on merge, stop: the deploy is a merge, not this procedure. See [references/deploy-gotchas.md](references/deploy-gotchas.md) for traps that recur across stacks. ## 2. Pre-flight (read-only, run in parallel) - `git status --short` and `git log --oneline origin/<branch>..HEAD`: what ships, and is it committed and pushed? Uncommitted code has no rollback point.