DevOps
ci-cd-pipeline
GitHub Actions / GitLab CI pipeline design: caching, parallel execution, secure deployment, and notification integration.
Install
clawhub install ci-cd-pipeline
Cross-tool: Claude Code ~/.claude/skills/ · Qoder ~/.qoder/skills/ · TRAE ~/.trae/skills/
When to Use
Trigger this skill when designing CI/CD pipelines, optimizing build speed, configuring auto-deployment, or troubleshooting pipeline failures.
Core Practices
Pipeline Structure
- Stage breakdown: lint → test → build → deploy
- Fast fail: lint and unit tests first, stop on failure
- Matrix builds: parallelize across versions/platforms
Caching Strategy
- Dependency cache:
actions/cache or GitLab CI cache
- Docker layer cache:
cache_from + BuildKit
- Reinstall only when lock file changes
Deployment
- Environment isolation: staging → production, manual approval gates
- Blue-green / canary deployment, avoid full rollout
- Rollback: keep previous image/artifact, one-click revert
- Secrets in repo/org encrypted variables, never hardcoded
Notifications
- Build failure: instant notification (Slack / Feishu / Email)
- Deploy success: include version number and change summary
- Regularly clean expired caches and old build artifacts