building-cicd-pipelines

name	building-cicd-pipelines
description	Execute use when you need to work with deployment and CI/CD. This skill provides deployment automation and pipeline orchestration with comprehensive guidance and automation. Trigger with phrases like "deploy application", "create pipeline", or "automate deployment".
allowed-tools	Read, Write, Edit, Grep, Glob, Bash(git:*), Bash(docker:*), Bash(kubectl:*)
version	1.0.0
author	Jeremy Longshore <[e-mail]>
license	MIT
compatible-with	claude-code, codex, openclaw
tags	["devops","deployment","ci-cd"]

Building CI/CD Pipelines

Current State

!ls .github/workflows/*.yml .gitlab-ci.yml Jenkinsfile .circleci/config.yml 2>/dev/null || echo 'No CI/CD config found'

Overview

Generate CI/CD pipeline configurations for GitHub Actions, GitLab CI, Jenkins, CircleCI, and Azure DevOps. Produce multi-stage workflows covering linting, testing, building container images, security scanning, and deploying to staging/production with proper gating and rollback mechanisms.

Prerequisites

• Git repository hosted on a supported platform (GitHub, GitLab, Bitbucket, Azure DevOps)
• Container runtime (Docker) if building images
• Target deployment environment credentials configured as pipeline secrets
• Test suite that can run headlessly (npm test, pytest, go test, etc.)
• Understanding of branching strategy (trunk-based, GitFlow, or environment branches)

Instructions

1. Scan the project for existing CI/CD configuration files (.github/workflows/, .gitlab-ci.yml, Jenkinsfile, .circleci/config.yml)
2. Identify the application stack: language, framework, test runner, package manager, and deployment target
3. Define pipeline stages: lint -> test -> build -> security-scan -> deploy-staging -> integration-test -> deploy-production
4. Generate the pipeline configuration file with appropriate triggers (push to main, PR events, tags)
5. Add caching for dependencies (node_modules, .pip-cache, Go modules) to reduce build times
6. Configure matrix builds for multiple language versions or OS targets where appropriate
7. Add secret references for deployment credentials, container registry tokens, and API keys (never hardcode)
8. Implement deployment gates: manual approval for production, automated rollback on health check failure
9. Add status badges and notifications (Slack, email) for build results
10. Validate the pipeline syntax using platform-specific tools (actionlint, gitlab-ci-lint)

Output

• Pipeline configuration files (.github/workflows/*.yml, .gitlab-ci.yml, Jenkinsfile)