deployment-pipeline-design_skill
- Python
20
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill nilecui/skillsbase --skill deployment-pipeline-design- SKILL.md8.3 KB
Overview
This skill designs multi-stage CI/CD pipelines that balance delivery speed with deployment safety. It defines stage organization, approval gates, security checks, progressive delivery strategies, and rollback patterns for reliable production rollouts. Use it to architect pipelines across GitHub Actions, GitLab CI, Azure Pipelines, or Kubernetes-based deployments.
How this skill works
The skill inspects desired environments, test suites, and release risk to recommend a staged flow: source → build → test → staging → approval → production → verification → rollback. It maps approval patterns (manual, time-delayed, multi-approver) and deployment strategies (rolling, blue-green, canary, feature flags) to implementation snippets and orchestration patterns. It also integrates monitoring checks, automated rollback triggers, and artifact/secrets handling guidance.
When to use it
- Architect a new CI/CD workflow for multiple environments
- Add approval gates or multi-approver controls before production
- Implement progressive delivery (canary, blue-green, rolling)
- Define automated rollback and verification steps
- Adopt GitOps practices or convert pipelines to declarative orchestration
Best practices
- Fail fast: run quick unit and lint checks early in the pipeline
- Parallelize independent jobs to reduce lead time
- Keep environment parity between staging and production
- Integrate security scans and secret stores into pipeline steps
- Automate verification and rollback based on health and metrics
- Document pipeline stages, deployment windows, and owner responsibilities
Example use cases
- Design a pipeline that builds, scans, deploys to staging, runs E2E tests, then requires manual approval for production
- Implement a canary rollout using Argo Rollouts with timed weight increases and automated metrics checks
- Add a multi-approver manual validation step in Azure Pipelines for high-risk releases
- Configure time-delayed production deployment in GitLab for scheduled releases
- Use feature flags to ship code behind switches for controlled exposure and instant rollback
FAQ
Choose based on risk and cost: rolling works for most apps with zero downtime; blue-green gives instant switchover but doubles infra temporarily; canary reduces risk by shifting traffic gradually and is best when you can observe metrics during rollout.
When should I require manual approval?
Require manual approval for high-risk changes (database migrations, breaking API changes) or when business stakeholders must sign off. Use multi-approver gates for critical systems and time-delays for scheduled windows.
How do I automate rollback safely?
Automate rollback by adding health and metric checks post-deploy; if thresholds (error rate, latency, failed health probes) breach, trigger a rollback command or undo deployment. Keep playbooks and quick manual rollback commands as backups.
