Skip to content

jeremylongshore/tons-of-skills-marketplace / plugins/devops/ci-cd-pipeline-builder/skills/building-cicd-pipelines

building-cicd-pipelines

Verified

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".

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)
  • Dockerfile for container builds (multi-stage, minimal base image)
  • Deployment scripts or Kubernetes manifests referenced by the pipeline
  • Environment-specific variable files for staging vs. production

Error Handling

ErrorCauseSolution
Pipeline triggered but no jobs runTrigger conditions (paths, branches) do not matchReview on: / only: / rules: filters and verify branch names
Docker build failed: layer cache missCache key changed or cache storage expiredUse content-based cache keys (hashFiles('**/package-lock.json')) and verify cache backend
Secret not foundSecret name mismatch or not set in pipeline settingsCheck secret names match exactly (case-sensitive) in repository/project settings
Deploy failed: unauthorizedExpired or incorrect deployment credentialsRotate credentials, update pipeline secrets, and verify IAM role/service account permissions
Tests pass locally but fail in CIEnvironment differences (OS, node version, timezone)Pin runtime versions in pipeline config; use matrix to test across environments

Examples

  • "Create a GitHub Actions workflow for a Node.js app: lint with ESLint, test with Jest, build Docker image, push to ECR, deploy to EKS staging on PR merge."
  • "Generate a GitLab CI pipeline with parallel test jobs, SAST scanning, and manual production deployment gate."
  • "Build a Jenkins pipeline that runs Python tests in a Docker agent, publishes coverage to SonarQube, and deploys via Terraform."

Resources

writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 323kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall