How do I install the Dockerize And Deploy skill?

Run npx skillmds@latest add rockclaver/dockerize-and-deploy in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Dockerize And Deploy safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Dockerize And Deploy?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Dockerize And Deploy free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Dockerize And Deploy?

rockclaver (@rockclaver) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Dockerize And Deploy by rockclaver — Agent Skill

Name: Dockerize And Deploy
Author: rockclaver

Dockerize And Deploy

Dockerizes a repo — Dockerfile, docker-compose with volumes, and a preflight script. Use to containerize an app, add Docker support, write a deployment pipeline, set up docker-compose, configure volumes, or deploy to production with Docker.

rockclaver ee59b10 4 files · 16.7 KB Updated Sep 17, 2026

File contents

Dockerize and Deploy

Containerize a repo and produce a deployment setup, one phase at a time.

Workflow

1. Audit

Identify runtime, services, datastores, build step, existing Docker files, and env vars. Propose phases before writing.

2. Phases

Dockerfile — multi-stage: builder installs/compiles, runtime copies artifacts only, non-root user, pinned base image (e.g. node:20.11-alpine), .dockerignore excludes node_modules/.env/.git.
docker-compose — dev stack: source mounts for hot reload, debug ports, named volumes.
Production compose (docker-compose.prod.yml) — no source mounts, restart: unless-stopped, healthchecks, explicit volumes, mem_limit/cpus limits. See REFERENCE.md.
Pre-flight — copy scripts/preflight.sh into the project; validates env vars, Docker, port conflicts, DB reachability, dry-run build. Run: bash scripts/preflight.sh.
Deploy — scripts/deploy.sh: run preflight.sh (abort on fail) → pull/build image → run migrations → rolling restart → health-check → print status.

Merge or skip phases for simple repos.

3. Verify after each phase

docker build -t app:test .           # Dockerfile compiles
docker compose config                # compose files are valid YAML
docker compose up -d && docker compose ps  # services start healthy
bash scripts/preflight.sh            # pre-flight passes

Guardrails

Never embed secrets in Docker/compose files.
Always run containers as a non-root user.
No latest image tags in production — pin versions.
DB volumes: named volumes only, never host bind mounts.
No .env.example? Create one first.

References

REFERENCE.md — volume/healthcheck patterns, resource limits, multi-stage examples by runtime, rolling deploy strategies.

---name: dockerize-and-deploydescription: Dockerizes a repo — Dockerfile, docker-compose with volumes, and a preflight script. Use to containerize an app, add Docker support, write a deployment pipeline, set up docker-compose, configure volumes, or deploy to production with Docker.---# Dockerize and DeployContainerize a repo and produce a deployment setup, one phase at a time.## Workflow### 1. AuditIdentify runtime, services, datastores, build step, existing Docker files, and env vars. Propose phases before writing.### 2. Phases1. **Dockerfile** — multi-stage: builder installs/compiles, runtime copies artifacts only, non-root user, pinned base image (e.g. `node:20.11-alpine`), `.dockerignore` excludes `node_modules`/`.env`/`.git`.2. **docker-compose** — dev stack: source mounts for hot reload, debug ports, named volumes.3. **Production compose** (`docker-compose.prod.yml`) — no source mounts, `restart: unless-stopped`, healthchecks, explicit volumes, `mem_limit`/`cpus` limits. See [REFERENCE.md](REFERENCE.md).4. **Pre-flight** — copy `scripts/preflight.sh` into the project; validates env vars, Docker, port conflicts, DB reachability, dry-run build. Run: `bash scripts/preflight.sh`.5. **Deploy** — `scripts/deploy.sh`: run `preflight.sh` (abort on fail) → pull/build image → run migrations → rolling restart → health-check → print status.Merge or skip phases for simple repos.### 3. Verify after each phase```bashdocker build -t app:test . # Dockerfile compilesdocker compose config # compose files are valid YAMLdocker compose up -d && docker compose ps # services start healthybash scripts/preflight.sh # pre-flight passes```## Guardrails- Never embed secrets in Docker/compose files.- Always run containers as a non-root user.- No `latest` image tags in production — pin versions.- DB volumes: named volumes only, never host bind mounts.- No `.env.example`? Create one first.## References- [REFERENCE.md](REFERENCE.md) — volume/healthcheck patterns, resource limits, multi-stage examples by runtime, rolling deploy strategies.

Frequently asked questions