Skip to main content
command

setup-ci-cd-pipeline — Claude Code command: what it does, install

Configures CI/CD pipelines for GitHub Actions, GitLab CI, Azure Pipelines, or Jenkins with automated testing, security gates, and deployment flows.

Install into Claude Code · claude-code-templates All methods and platforms ↓
npx claude-code-templates@latest --command setup/setup-ci-cd-pipeline
Open on GitHub

What setup-ci-cd-pipeline does

This command generates continuous integration and deployment pipelines for GitHub Actions, GitLab CI, Azure Pipelines, or Jenkins. It inspects the project first. The agent checks git remote, detects .gitlab-ci.yml or .github directories, and reads @package.json or @Dockerfile to identify your framework.

The generated workflow covers compilation, unit and end-to-end tests, code coverage, and vulnerability audits. It also writes deployment steps for staging and production, rollback hooks, and rollout patterns like canary or blue-green releases. Because the prompt relies on Read, Write, Edit, and Bash tools, the agent requires terminal access to inspect the repository.

What it helps with

  • set up automated testing and linting triggers on code push
  • generate pipeline configurations for GitHub Actions, GitLab CI, or Jenkins
  • add vulnerability scans and security gates to the build cycle
  • configure staging and production deployments with rollback support

Example prompts for the agent

  • /setup-ci-cd-pipeline --github-actions
  • /setup-ci-cd-pipeline --gitlab-ci
  • /setup-ci-cd-pipeline --jenkins

How to install setup-ci-cd-pipeline

1claude-code-templates

npx claude-code-templates@latest --command setup/setup-ci-cd-pipeline

2Manually: put the files in place

.claude/commands/setup-ci-cd-pipeline.md

Call it with /setup-ci-cd-pipeline. For all projects use ~/.claude/commands/

Questions about setup-ci-cd-pipeline

How do I install setup-ci-cd-pipeline in Claude Code?

Run npx claude-code-templates@latest --command setup/setup-ci-cd-pipeline in your terminal to save the command to .claude/commands/setup-ci-cd-pipeline.md.

What does setup-ci-cd-pipeline do?

It scans the repository for test files, Docker manifests, and existing CI setups, then writes build, test, and deployment configurations.

Which CI platforms does setup-ci-cd-pipeline support?

The command supports GitHub Actions, GitLab CI, Azure Pipelines, and Jenkins. You select the platform using flags such as --github-actions or --gitlab-ci.

Source text

setup-ci-cd-pipeline.md · MIT
---
allowed-tools: Read, Write, Edit, Bash
argument-hint: "[platform] | --github-actions | --gitlab-ci | --azure-pipelines | --jenkins"
description: Setup comprehensive CI/CD pipeline with automated testing, deployment, and monitoring
---

# Setup CI/CD Pipeline

Setup comprehensive CI/CD pipeline with automated workflows and deployments: **$ARGUMENTS**

## Current Repository State

- Version control: !`git remote -v | head -1` (GitHub, GitLab, etc.)
- Existing CI: !`find . -name ".github" -o -name ".gitlab-ci.yml" -o -name "azure-pipelines.yml" | wc -l`
- Test framework: @package.json or testing files detection
- Deployment config: @Dockerfile or deployment manifests

## Task

Implement production-ready CI/CD pipeline with comprehensive automation and best practices:

**Platform Choice**: Use $ARGUMENTS to specify GitHub Actions, GitLab CI, Azure Pipelines, or Jenkins

**Pipeline Architecture**:
1. **Build Automation** - Code compilation, dependency installation, artifact creation
2. **Testing Strategy** - Unit tests, integration tests, e2e tests, code coverage reporting
3. **Quality Gates** - Linting, security scanning, vulnerability assessment, code quality metrics
4. **Deployment Automation** - Staging deployment, production deployment, rollback mechanisms
5. **Environment Management** - Infrastructure provisioning, configuration management, secrets handling
6. **Monitoring Integration** - Performance monitoring, error tracking, deployment notifications

**Advanced Features**: Parallel job execution, matrix builds, deployment strategies (blue-green, canary), and multi-environment support.

**Security & Compliance**: Secure credential management, compliance checks, audit trails, and approval workflows.

**Output**: Complete CI/CD pipeline with automated testing, secure deployments, monitoring integration, and comprehensive documentation.

© davila7 · MIT · davila7/claude-code-templates

Similar slash commands

All slash commands for DevOps and infrastructure →

From the same set495

The whole set →
update-dependencies This command checks for outdated packages and security issues, then guides dependency updates by strategy. Use it for routine upgrades or a security-focused pass. 356installs developer-growth-analysis Reads your recent Claude chat history, spots skill gaps in your work, and sends a growth report to your Slack DMs. 355installs log Writes a finished task's report into your tracker or notes: time spent, status, commits. Useful when the coding happens in Claude but the record lives in Linear or Obsidian. 351installs create-worktrees Pulls every open pull request through GitHub CLI and sets up a separate git worktree for each branch under ./tree/. Useful when you want several PRs checked out at once without switching branches in the main checkout. 351installs excalidraw This skill routes Excalidraw file work to subagents so large JSON diagrams stay out of the main context. Use it for flowcharts and architecture visuals. 342installs develop-web-game This skill lays out a development and testing loop for HTML and JavaScript games. Use it while adding game features and checking each meaningful change in a browser. 342installs branch-cleanup A Claude slash command that finds merged and stale branches, checks them before deletion, and tidies up both local and remote refs. 342installs pentest-checklist A skill that walks you through pentest planning: objectives, scope, environment prep, tester selection and monitoring. Useful before a security assessment. 336installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor