技能 deployment-pipeline-design
🚀

deployment-pipeline-design

安全 🌐 網路存取⚙️ 外部命令🔑 環境變數

تصميم خطوط أنابيب CI/CD آمنة

也可從以下取得: sickn33

Many teams deploy without clear stages or approvals and face risky releases. This skill gives proven pipeline structures and rollout strategies to improve safety and speed.

支援: Claude Codex Code(CC)
📊 69 充足
1

下載技能 ZIP

2

在 Claude 中上傳

前往 設定 → 功能 → 技能 → 上傳技能

3

開啟並開始使用

測試它

正在使用「deployment-pipeline-design」。 Design a CI/CD pipeline with approval and rollback for a Kubernetes service.

預期結果:

  • Stages: Source, Build, Test, Staging Deploy, Integration Tests, Approval, Production Deploy, Verify, Rollback
  • Approval: Manual gate after staging with a named approver group
  • Deployment: Canary rollout with stepwise traffic shifts and health checks

正在使用「deployment-pipeline-design」。 How do I implement blue-green deployment for a database-backed application?

預期結果:

  • Create parallel production environments (blue=current, green=new)
  • Deploy green version alongside blue with identical infrastructure
  • Run smoke tests against green before switching traffic
  • Keep blue running for instant rollback if issues arise

正在使用「deployment-pipeline-design」。 What metrics should I track to measure deployment success?

預期結果:

  • Deployment frequency: how often you deploy to production
  • Lead time: time from code commit to production deployment
  • Change failure rate: percentage of deployments causing failures
  • Mean time to recovery: how quickly you restore service after incidents

安全審計

安全
v4 • 1/17/2026

Pure documentation skill containing only markdown explanations and YAML/JSON example snippets. All static findings are false positives triggered by example code patterns in documentation. No executable scripts, network calls, filesystem access, or credential handling code exists. The skill is a reference guide for CI/CD architecture patterns.

2
已掃描檔案
533
分析行數
3
發現項
4
審計總數
審計者: claude 查看審計歷史 →

品質評分

38
架構
100
可維護性
85
內容
21
社群
100
安全
91
規範符合性

你能建構什麼

خطة خط أنابيب متعددة المراحل

إنشاء تصميم CI/CD مرحلي مع الموافقات وفحوصات السلامة لإصدارات الإنتاج.

توحيد استراتيجية النشر

اختيار استراتيجيات التدحرج أو الأزرق والأخضر أو الكناري لإصدارات منصة متسقة.

دليل حوكمة الإصدارات

تعريف بوابات الموافقة وخطوات التحقق للتغييرات المُتحكَّم بها في الإنتاج.

試試這些提示

خط أنابيب البداية
Draft a simple multi-stage CI/CD pipeline for a web app with build, test, staging, approval, and production deploy.
تصميم بوابة الموافقة
Propose approval gate patterns for GitHub Actions and Azure Pipelines, including who approves and when.
اختيار الاستراتيجية
Compare rolling, blue-green, and canary strategies for a high-traffic API and recommend one.
مخطط خط الأنابيب الكامل
Design a full CI/CD pipeline with security scans, staging tests, approval, canary deploy, verification, and rollback.

最佳實務

  • Fail fast with quick tests before long-running jobs
  • Use environment parity between staging and production
  • Automate rollback based on health checks and error rates

避免

  • Skipping approval gates for high-risk production changes
  • Deploying without post-deploy verification or monitoring
  • Using a single stage for build, test, and deploy

常見問題

What platforms does this work with?
The examples cover GitHub Actions, GitLab CI, and Azure Pipelines, and the concepts apply to most CI/CD systems.
What are the limits of this skill?
It provides guidance and examples only and does not execute or configure pipelines.
Can it integrate with existing tools?
Yes, the patterns align with common tools like Kubernetes, Argo Rollouts, and security scanners.
Does it access my data or secrets?
No, it is static documentation and does not access files, secrets, or networks.
What if my pipeline fails?
Use the rollback and verification guidance to isolate issues and restore a stable release.
How is this different from a template skill?
This focuses on architecture decisions and tradeoffs rather than providing runnable templates.