# ci-setup

ci-setup — a Claude slash command that builds out a CI/CD pipeline: it reads your stack, picks a platform and writes the config for tests, Docker and deploys.

- command · `type=command` · Claude Code, Codex, GitHub Copilot, Gemini CLI · ★ 1357 repo stars
- Author: qdhenry
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/qdhenry/Claude-Command-Suite/tree/HEAD/.claude/commands/deploy/ci-setup.md
- Updated: 2026-03-01
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/qdhenry-ci-setup

## What it does

The command takes the agent through CI/CD setup in stages: it inspects the stack and the deploy requirements, picks a platform such as GitHub Actions, GitLab CI, Jenkins, CircleCI, Azure DevOps or AWS CodePipeline, then writes the pipeline config. Whatever you type after the call lands in `$ARGUMENTS` and shapes that plan.

20 steps sit inside: a test matrix, dependency caching, a multi-stage `Dockerfile`, release strategies like blue-green and canary, database migrations, vulnerability scanning, rollback, Slack or Teams notifications, deployment audits. YAML samples cover GitHub Actions and GitLab CI, so you are not starting from an empty file.

One step needs a secret: the Snyk scan reads `SNYK_TOKEN` from repository settings, and the job fails without it. Closing tips stay short: catch failures early, let independent jobs run side by side.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/commands/ci-setup.md` — Call it with /ci-setup. For all projects use ~/.claude/commands/

### Codex

**Manually: put the files in place**
- File: `~/.codex/prompts/ci-setup.md` — Call it with /prompts:ci-setup. Codex marks this format deprecated in favour of skills

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/ci-setup.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/ci-setup.toml` — Gemini stores commands as TOML: the prompt text goes into the prompt field

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/qdhenry/Claude-Command-Suite/tree/HEAD/.claude/commands/deploy/ci-setup.md

## When to use it
- scaffold a GitHub Actions pipeline from scratch
- pick a CI platform that fits the stack
- wire up secrets and per-environment variables
- add a multi-stage `Dockerfile` and build caching
- set up rollback and deploy failure alerts

## Example prompts
- \`/ci-setup` Node.js app, tests run with `npm test`, deploy to staging from `develop`
- \`/ci-setup` build a GitHub Actions pipeline with a Node version matrix and `node_modules` caching
- \`/ci-setup` add vulnerability scanning and automatic rollback when a deploy fails

## Similar
- [devops-infrastructure](https://affpapa.org/en/nevibecode/skills/devops-infrastructure.md) — skill · ★ 1424 repo stars
- [devops-engineer](https://affpapa.org/en/nevibecode/skills/devops-engineer.md) — skill · 12400 installs
- [cicd-pipeline-setup](https://affpapa.org/en/nevibecode/skills/cicd-pipeline-setup.md) — skill · 505 installs
- [deployment-engineer](https://affpapa.org/en/nevibecode/skills/deployment-engineer.md) — skill · 685 installs
- [github-actions-workflow](https://affpapa.org/en/nevibecode/skills/github-actions-workflow.md) — skill · 629 installs
- [devops-cicd](https://affpapa.org/en/nevibecode/skills/devops-cicd.md) — skill · 610 installs

From the same set: [qdhenry/claude-command-suite](https://affpapa.org/en/nevibecode/by/qdhenry/claude-command-suite.md) — 112 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
