CI CD Pipeline Design
GitHub Actions, GitLab CI, Jenkins; stages, artifacts, caching, and deployment automation.
Install
/plugin marketplace add sethdford/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sethdford/claude-skills --skill ci-cd-pipeline-designgit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/engineer/devops-practices/skills/ci-cd-pipeline-design ~/.claude/skills/ci-cd-pipeline-designPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# CI/CD Pipeline Design Automating build, test, and deployment through continuous integration and deployment. ## Context You are designing a CI/CD pipeline. Define stages, dependencies, and success criteria. ## Domain Context - **Build**: Compile, package; generate artifacts - **Test**: Run unit, integration, E2E tests; quality gates - **Deploy**: Canary, blue-green, rolling; minimize downtime - **Artifacts**: Build outputs; cache for speed - **Secrets**: Never in code; use secrets manager ## Instructions 1. **Identify Stages**: Build, test, deploy, monitor 2. **Define Triggers**: On commit? Pull request? Manual? 3. **Parallelize**: Run independent jobs in parallel 4. **Cache**: Cache dependencies, build outputs for speed 5. **Gate**: Quality gates; don't deploy if tests fail 6. **Secrets**: Use secrets manager; never in logs 7. **Artifacts**: Store and reuse build artifacts ## Anti-Patterns - Slow pipelines (>15 min); too long, feedback is slow - Secrets in code or logs; instant compromise - No quality gates; broken code gets deployed - Parallelization ignored; sequential is slow - No caching; rebuild everything every time ## Further Reading - Google Cloud CI/CD Best Practices - GitHub Actions documentation - GitLab CI/CD documentation
Details
- Skill name
ci-cd-pipeline-design- Repository
- sethdford/claude-skills
- Path
engineer/devops-practices/skills/ci-cd-pipeline-design/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
What does the CI CD Pipeline Design skill do?
GitHub Actions, GitLab CI, Jenkins; stages, artifacts, caching, and deployment automation.
How do I install the CI CD Pipeline Design skill?
Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is CI CD Pipeline Design popular?
It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.
Related skills
A B Test Design
48sethdford/claude-skills
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
A B Test Design Pm
48sethdford/claude-skills
Analytics and experimentation skill for product managers.
Abuse Case Design
48sethdford/claude-skills
Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.
Code Review Checklist
48sethdford/claude-skills
Systematic code review process, feedback templates, approval criteria, and review best practices.
Automated Review Setup
48sethdford/claude-skills
Set up automated code review tools (linters, SAST, dependency scanning) to reduce manual review burden. Use when configuring CI/CD toolchains.
Git Workflow
48sethdford/claude-skills
Feature branches, commit hygiene, rebasing vs. merging, and collaborative workflows.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.