ci
Generate a CI/CD pipeline — build, test, security scan, deploy. Supports GitHub Actions, GitLab CI, Bitbucket Pipelines.
@khaitrang1995Install SkillDevelopment
Skill
/stack
Generate a Docker Swarm stack file — services, deploy policy (replicas, placement, rolling update/rollback), overlay network.
Claude Code
$ npx -y skills add KhaiTrang1995/agentic-awesome-kits --skill stack --agent claude-code
Codex
$ npx skills add KhaiTrang1995/agentic-awesome-kits --skill stack -a codex -y
Cursor
$ npx skills add KhaiTrang1995/agentic-awesome-kits --skill stack -a cursor -y
Gemini CLI
$ npx skills add KhaiTrang1995/agentic-awesome-kits --skill stack -a gemini-cli -y
GitHub Copilot
$ npx skills add KhaiTrang1995/agentic-awesome-kits --skill stack -a github-copilot -y
OpenCode
$ npx skills add KhaiTrang1995/agentic-awesome-kits --skill stack -a opencode -y
Windsurf
$ npx skills add KhaiTrang1995/agentic-awesome-kits --skill stack -a windsurf -y
SKILL.md
stack.SKILL.mdname: stack
description: Generate a Docker Swarm stack file — services, deploy policy (replicas, placement, rolling update/rollback), overlay network.
user-invocable: true
argument-hint: "<stack description> [--replicas <n>] [--with-db] [--with-proxy]"
/stack — Generate a Swarm Stack File
Input examples
/stack .NET API + Angular + Postgres --replicas 3
/stack worker service --replicas 2 --with-db
/stack fullstack --with-proxy (adds a Traefik front, see traefik-proxy-stack.yml)
Process
1. Detect the services and their dependency order. 2. For each service: base image (reuse `docker-kit/docker-conventions.md` for the Dockerfile side), `deploy:` stanza per `swarm-conventions.md`, healthcheck. 3. Sensitive values → reference an `external: true` secret, never an inline env var — see `/secret`. 4. Attach all services to a stack-scoped overlay network. 5. L1 approval → Write.
Mandatory rules
- **`deploy.replicas` explicit** for every service — never rely on the Swarm default of 1
- **`resources.limits` + `.reservations`** both set
- **`update_config` + `rollback_config`** both set — a rollout with no rollback plan is incomplete
- **Secrets via `docker secret`** — never plain env vars for passwords/keys/tokens
- **Stateful services** (db, anything with local volume) get `placement.constraints`
- **No inline Ingress** — routing by hostname needs a proxy front (`--with-proxy`), Swarm has no Ingress resource
Output
docker-stack.yml
.env.example (placeholders only — real secrets are never written to a file the agent generates)
References
- @.claude/rules/swarm-conventions.md
- @../../docker-kit/.claude/rules/docker-conventions.md
Read more
name: stack description: Generate a Docker Swarm stack file — services, deploy policy (replicas, placement, rolling update/rollback), overlay network. user-invocable: true argument-hint: "<stack description> [--replicas <n>] [--with-db] [--with-proxy]"
/stack — Generate a Swarm Stack File
Input examples
/stack .NET API + Angular + Postgres --replicas 3 /stack worker service --replicas 2 --with-db /stack fullstack --with-proxy (adds a Traefik front, see traefik-proxy-stack.yml)
Process
1. Detect the services and their dependency order. 2. For each service: base image (reuse `docker-kit/docker-conventions.md` for the Dockerfile side), `deploy:` stanza per `swarm-conventions.md`, healthcheck. 3. Sensitive values → reference an `external: true` secret, never an inline env var — see `/secret`. 4. Attach all services to a stack-scoped overlay network. 5. L1 approval → Write.
Mandatory rules
- **`deploy.replicas` explicit** for every service — never rely on the Swarm default of 1
- **`resources.limits` + `.reservations`** both set
- **`update_config` + `rollback_config`** both set — a rollout with no rollback plan is incomplete
- **Secrets via `docker secret`** — never plain env vars for passwords/keys/tokens
- **Stateful services** (db, anything with local volume) get `placement.constraints`
- **No inline Ingress** — routing by hostname needs a proxy front (`--with-proxy`), Swarm has no Ingress resource
Output
docker-stack.yml .env.example (placeholders only — real secrets are never written to a file the agent generates)
References
- @.claude/rules/swarm-conventions.md
- @../../docker-kit/.claude/rules/docker-conventions.md
Stats
10
Stars
5
Forks
Maintained
Maintenance
Python
Language
Last commit
Created
Ships withagentic-awesome-kits
Reusable AI Skill Kits for coding agents (Claude Code and any other subagent/slash-command-compatible tool).
1032 skills
Stars on GitHub
Momentum
- stars in total
- 10
Other skills on agentic-awesome-kits.
@khaitrang1995Install Skillcompose
Generate docker-compose.yml — multi-service, network, volumes, healthcheck.
@khaitrang1995Install Skilldockerfile
Generate an optimized Dockerfile — multi-stage build, security hardening, small image size.
@khaitrang1995Install Skillsecret
Generate Swarm secret/config management — external secret references, versioned rotation, config mounts.
@khaitrang1995Install Skillservice
Generate or update a single Swarm service definition — scaling, resource limits, rolling update policy, health check.
@khaitrang1995Install Skillelk-health
ELK health checklist — cluster status, shards, ILM, disk watermarks, ingest lag, pipeline errors. Docs only.
@khaitrang1995Install SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about stack.
- Which coding agents can use stack?
- stack installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.