One-click install
npx skills add https://github.com/david-driscoll/stargate-command-cluster --skill promotion-pipeline-david-driscoll
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: promotion-pipeline
Source: https://github.com/david-driscoll/stargate-command-cluster/tree/main/.agents/skills/promotion-pipeline
Command: npx skills add https://github.com/david-driscoll/stargate-command-cluster --skill promotion-pipeline-david-driscoll

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, docker, flux, kubectl, gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

The promotion-pipeline skill helps you determine why a merged change has not reached the live Kubernetes cluster by tracing it through the end-to-end OCI artifact promotion lifecycle and its validation gates.

Core Features & Use Cases

  • End-to-end pipeline tracing: Follow the build → integration validation → promotion → live deployment stages using concrete GitHub Actions, GHCR, Flux reconciliation, and alerting checkpoints.
  • Artifact/tag strategy debugging: Diagnose issues based on the exact OCI tags (rc, sha, integration, validated, and stable semver) and how they move between systems.
  • Fast recovery and manual promotion: Provide an emergency manual promotion path when automation fails, including fallback tagging via Flux if required.
  • Key use cases: Troubleshoot changes stuck in integration, investigate live not updating, interpret GitHub Actions workflow failures, and validate OCI artifact tags in GHCR.

Quick Start

Ask the skill to trace why a specific commit SHA has not appeared on the live cluster and to walk the exact checks from build, through OCIRepository semver/conditions, to the validation-success alert and the stable tag promotion.

Frequently Asked Questions about promotion-pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why is my Flux GitOps deployment not updating with the latest OCI artifact tag?

Flux GitOps deployments fail to update when OCIRepository semver constraints, reconciliation status, or validation gates block the promotion pipeline from moving the stable tag forward. Tracing the build-to-integration-to-promotion flow identifies the exact stuck checkpoint.

How do I trace a stuck OCI artifact promotion through GitHub Actions and GHCR?

Trace a stuck OCI artifact promotion by following the build, integration validation, repository_dispatch, and Flux reconciliation checkpoints. Validate the exact GHCR tag ordering from sha and rc through integration and validated up to the stable semver tag.

How do I manually promote or rollback an OCI artifact in a Flux Kubernetes cluster when automation breaks?

Manually promote or rollback an OCI artifact in a Flux Kubernetes cluster by applying emergency fallback tagging via Flux when automation breaks. This bypasses the broken GitHub Actions workflow to force the live deployment to the desired validated tag.

What tools do I need to debug an OCI artifact promotion pipeline using Flux and GHCR?

Debugging an OCI artifact pipeline requires bash, docker, flux, kubectl, and gh command line tools. These dependencies allow you to inspect GHCR artifact tags, check Flux kustomization reconciliation, and trigger GitHub Actions workflows.

How do I diagnose GitHub Actions workflow failures blocking integration validation for OCI artifacts?

Diagnose GitHub Actions workflow failures blocking integration validation by checking the repository_dispatch event flow and verifying idempotency behavior during the build-to-integration stage. Validate that the integration tag was correctly applied in GHCR before promotion.