Agent skill · software engineering · jeremylongshore
building-cicd-pipelines
Execute use when you need to work with deployment and CI/CD.
Why this skill is useful
Adds executable scripts for generating CI/CD pipeline configurations across multiple platforms, including deployment automation and error handling.
What it needs
Requires docker installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
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 (nodemodules, .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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/building-cicd-pipelines--23f3ae