gha-pipelines

Design and update GitHub Actions CI/CD workflows for repository validation and OCI promotion.

1|Updated Apr 6, 2025
One-click install
npx skills add https://github.com/david-driscoll/stargate-command-cluster --skill gha-pipelines
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gha-pipelines
Source: https://github.com/david-driscoll/stargate-command-cluster/tree/main/.agents/skills/gha-pipelines
Command: npx skills add https://github.com/david-driscoll/stargate-command-cluster --skill gha-pipelines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you create and modify GitHub Actions CI/CD workflows for the homelab repository without breaking conventions or promotion pipelines.

Core Features & Use Cases

  • GitHub Actions workflow authoring with guardrails: Produces validation, build, and promotion workflows that follow repo-specific patterns for tool setup, permissions, and triggers.
  • OCI artifact promotion integration: Explains the constraints needed for validated-to-stable tagging, including how idempotency works with Flux alert-driven reconciliation cycles.
  • Homelab-specific validation coverage: Supports a workflow inventory approach for Kubernetes and infrastructure directories, including schema linting and template expansion steps.

Quick Start

Ask the AI to generate a new PR validation workflow for your Kubernetes domain that follows the repo’s paths filter conventions and uses the mise-based tool setup.

Frequently Asked Questions about gha-pipelines

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

FAQPage Schema
How do I create GitHub Actions workflows for CI/CD validation without breaking existing promotion pipelines?

GitHub Actions CI/CD workflows should follow repo-specific patterns for tool setup, minimal permissions, and correct path-based triggers to ensure validation stages do not disrupt existing promotion pipelines.

How does OCI artifact promotion work with Flux reconciliation cycles?

OCI artifact promotion requires idempotent, validated-to-stable tagging that aligns with Flux alert-driven reconciliation cycles, preventing duplicate deployments during continuous reconciliation loops.

What is the best way to manage tool versions in GitHub Actions workflows?

Managing tool versions in GitHub Actions workflows requires a consistent mise-based setup, ensuring uniform environment configuration across validation, build, and OCI promotion stages.

How do I add path-based triggers and workflow_dispatch support to Kubernetes validation workflows?

Kubernetes validation workflows require correct path-based triggers using paths filter conventions and must include workflow_dispatch support to allow manual execution alongside automated PR validation.

Why does my GitHub Actions workflow fail during schema linting and template expansion?

Schema linting and template expansion failures often occur when workflow inventory approaches do not properly cover Kubernetes and infrastructure directories or lack proper mise-based tool versioning.

Can I use this GitHub Actions workflow authoring approach for infrastructure directories outside of Kubernetes?

Yes, the workflow inventory approach supports both Kubernetes and infrastructure directories, applying schema linting, template expansion, and path-based triggers to ensure comprehensive validation coverage.