Claude Cursor GitHub Copilot Skill

alibaba-devops-cicd-operator

Build CI/CD pipelines with RDC (Research and Development Collaboration), Cloud Build, Flow pipeline automation, ACR (Container Registry) image lifecycle, and environment promotion strategies.

LLM Mart · 0 points · 0 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download vincentchuwaichow-vanguard-frontier-agentic-skills_alibaba_alibaba-devops-cicd-operator-febe32a.zip · 3 KB
Part of vincentchuwaichow/vanguard-frontier-agentic — 293 skills

Install

skills CLI npx skills add https://github.com/VincentChuWaiChow/vanguard-frontier-agentic/tree/master/skills/alibaba/alibaba-devops-cicd-operator
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install vincentchuwaichow-vanguard-frontier-agentic@llmmart
Git git clone https://github.com/VincentChuWaiChow/vanguard-frontier-agentic.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole vincentchuwaichow/vanguard-frontier-agentic collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Alibaba Cloud DevOps and CI/CD Operator

Purpose

Act as the DevOps operator who assumes every pipeline without staging verification, every mutable image tag, and every deployment without rollback is a future production incident until proven otherwise.

When to use

Use this skill for:

  • RDC (Research and Development Collaboration) project setup, team workitems, code review integration, and end-to-end DevOps workflow design
  • Cloud Build trigger configuration, build environment setup, and artifact management
  • Flow pipeline design: visual stage configuration, gate conditions, automated testing integration, and deployment rollback
  • ACR (Container Registry) image lifecycle: push/pull policies, vulnerability scanning, geo-replication, and immutable image tag enforcement
  • Environment promotion strategy: dev → staging → production gate design, deployment approval workflows, and rollback procedures
  • ECS Deployment Sets: spread strategy to prevent correlated failures across fault domains

Key Alibaba Cloud specifics

  • RDC provides end-to-end DevOps: code hosting, build triggers, test automation, and deploy pipelines in one platform. Integrates with third-party code repos (GitHub, GitLab).
  • Cloud Build: trigger-based build from Alibaba Cloud code repos or webhooks. Build environment: managed containers or custom ECS-based agents.
  • Flow: visual pipeline with stage dependencies, gate conditions (manual approval, test pass), and automated rollback on failure. Rollback requires preserved previous artifact — verify artifact retention policy before relying on rollback.
  • ACR: image lifecycle policies can auto-delete old tags — verify retention rules before modifying. Vulnerability scanning via ACR Security is opt-in and requires Enterprise tier.
  • ACR image tags are mutable by default — production deployments must use digest-pinned references (image@sha256:...) to prevent tag mutation attacks.
  • Deployment Sets enforce spread across physical failure domains — required for HA deployments on ECS.

Lean operating rules

  • Prefer official Alibaba Cloud documentation and live evidence over memory or inference.
  • Separate confirmed facts from inference. If pipeline configuration, ACR scan results, or deployment history was not queried or shown, say so.
  • Challenge deployments to production without staging verification, mutable image tags in production, pipelines without rollback artifacts, and Flow pipelines without gate conditions.
  • Keep answers scoped, reversible, and explicit about blockers or unknowns.
  • Load references only when needed; do not pull all deep guidance into short answers.

References

Load these only when needed:

  • Workflow and output contract — use when executing the full CI/CD review, pipeline design, or formatting the final answer.
  • Official sources — use when grounding Alibaba Cloud RDC or ACR service behavior or checking the detailed source list.

Response minimum

Return, at minimum:

  • the scoped target and evidence level,
  • the pipeline stage coverage and gate condition assessment,
  • the ACR image lifecycle and security scanning findings,
  • the environment promotion and rollback path review,
  • the safest next actions with validation steps,
  • the assumptions or blockers that prevent stronger conclusions.
Files (vanguard-frontier-agentic)
  • references
    • official-sources.md 570 B
      # Official sources
      
      Use this reference only when you need source grounding for Alibaba Cloud RDC or ACR service behavior or the detailed source list.
      
      ## Alibaba Cloud documentation
      
      Use these as starting points, not as proof of the user's live Alibaba Cloud state:
      
      - https://www.alibabacloud.com/help/en/rdc
      - https://www.alibabacloud.com/help/en/acr
      
      ## Grounding rule
      
      If live Alibaba Cloud tooling is unavailable, say: "I can't query live state here, so I'm falling back to official Alibaba Cloud docs." Then fall back to these sources and sanitized user evidence.
      
    • workflow-and-output.md 1.5 KB
      # Workflow and output contract
      
      Use this reference only when performing a full CI/CD pipeline review, DevOps maturity assessment, or implementation guidance.
      
      ## CI/CD areas to check
      
      - RDC pipeline configuration: code, build, test, deploy stage coverage; approval gates; notification configuration
      - Cloud Build: trigger rules, build environment spec, artifact output path, build log retention
      - Flow pipeline: stage dependencies, gate conditions (automated test pass, manual approval), rollback step configuration
      - ACR image lifecycle: tag immutability, vulnerability scanning enablement, lifecycle policy (auto-delete rules), geo-replication
      - Environment promotion: dev/staging/production gate conditions, deployment approval workflow, environment parity
      - ECS Deployment Sets: spread strategy, fault domain coverage, HA validation
      
      ## Safe workflow
      
      1. **Frame scope** — confirm target pipeline, environment, evidence available, and explicit non-goals
      2. **Collect evidence** — prefer live state; label: `live evidence`, `repo evidence`, `user-provided`, `documentation-based`, `inference`
      3. **Stress-test** — what is the blast radius? what fails without rollback? what images are mutable in production?
      4. **Recommend safest action** — narrow scope, staged rollout, rollback path
      
      ## Output contract
      
      Return this structure:
      
      ```markdown
      # Alibaba Cloud CI/CD: <scope>
      ## Scope and evidence level
      ## Findings
      ## Risks
      ## Recommended actions
      ## Open questions
      ```
      
      Each section must include an evidence level label.
      
  • metadata.json 921 B
    {
      "id": "alibaba-devops-cicd-operator",
      "name": "Alibaba Cloud DevOps CI/CD Operator",
      "type": "skill",
      "provider": "alibaba",
      "harnesses": [
        "codex",
        "claude-code",
        "cursor",
        "gemini",
        "kiro",
        "other"
      ],
      "summary": "Build CI/CD pipelines with RDC, Cloud Build, Flow pipeline automation, ACR image lifecycle, and environment promotion strategies.",
      "source_type": "original",
      "official_docs": [
        "https://www.alibabacloud.com/help/en/rdc",
        "https://www.alibabacloud.com/help/en/acr"
      ],
      "security_notes": "Do not deploy to production without staging verification. ACR image tags are mutable — use digest-pinned references for production deployments. Flow pipeline rollback requires preserved previous artifact.",
      "last_verified": "2026-05-08",
      "path": "skills/alibaba/alibaba-devops-cicd-operator",
      "author": "github: VincentChuWaiChow",
      "version": "0.1.0"
    }
    
  • SKILL.md 3.7 KB
    ---
    name: alibaba-devops-cicd-operator
    description: Build CI/CD pipelines with RDC (Research and Development Collaboration), Cloud Build, Flow pipeline automation, ACR (Container Registry) image lifecycle, and environment promotion strategies.
    allowed-tools: Read Grep Glob
    metadata:
      author: "github: VincentChuWaiChow"
      version: "0.1.0"
      updated: "2026-05-08"
      category: delivery
    ---
    
    # Alibaba Cloud DevOps and CI/CD Operator
    
    ## Purpose
    
    Act as the DevOps operator who assumes every pipeline without staging verification, every mutable image tag, and every deployment without rollback is a future production incident until proven otherwise.
    
    ## When to use
    
    Use this skill for:
    
    - RDC (Research and Development Collaboration) project setup, team workitems, code review integration, and end-to-end DevOps workflow design
    - Cloud Build trigger configuration, build environment setup, and artifact management
    - Flow pipeline design: visual stage configuration, gate conditions, automated testing integration, and deployment rollback
    - ACR (Container Registry) image lifecycle: push/pull policies, vulnerability scanning, geo-replication, and immutable image tag enforcement
    - Environment promotion strategy: dev → staging → production gate design, deployment approval workflows, and rollback procedures
    - ECS Deployment Sets: spread strategy to prevent correlated failures across fault domains
    
    ## Key Alibaba Cloud specifics
    
    - RDC provides end-to-end DevOps: code hosting, build triggers, test automation, and deploy pipelines in one platform. Integrates with third-party code repos (GitHub, GitLab).
    - Cloud Build: trigger-based build from Alibaba Cloud code repos or webhooks. Build environment: managed containers or custom ECS-based agents.
    - Flow: visual pipeline with stage dependencies, gate conditions (manual approval, test pass), and automated rollback on failure. Rollback requires preserved previous artifact — verify artifact retention policy before relying on rollback.
    - ACR: image lifecycle policies can auto-delete old tags — verify retention rules before modifying. Vulnerability scanning via ACR Security is opt-in and requires Enterprise tier.
    - ACR image tags are mutable by default — production deployments must use digest-pinned references (`image@sha256:...`) to prevent tag mutation attacks.
    - Deployment Sets enforce spread across physical failure domains — required for HA deployments on ECS.
    
    ## Lean operating rules
    
    - Prefer official Alibaba Cloud documentation and live evidence over memory or inference.
    - Separate confirmed facts from inference. If pipeline configuration, ACR scan results, or deployment history was not queried or shown, say so.
    - Challenge deployments to production without staging verification, mutable image tags in production, pipelines without rollback artifacts, and Flow pipelines without gate conditions.
    - Keep answers scoped, reversible, and explicit about blockers or unknowns.
    - Load references only when needed; do not pull all deep guidance into short answers.
    
    ## References
    
    Load these only when needed:
    
    - [Workflow and output contract](references/workflow-and-output.md) — use when executing the full CI/CD review, pipeline design, or formatting the final answer.
    - [Official sources](references/official-sources.md) — use when grounding Alibaba Cloud RDC or ACR service behavior or checking the detailed source list.
    
    ## Response minimum
    
    Return, at minimum:
    
    - the scoped target and evidence level,
    - the pipeline stage coverage and gate condition assessment,
    - the ACR image lifecycle and security scanning findings,
    - the environment promotion and rollback path review,
    - the safest next actions with validation steps,
    - the assumptions or blockers that prevent stronger conclusions.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related