gitops-workflow

Define the GitOps workflow for workload onboarding and ArgoCD sync diagnosis.

1|Updated Nov 27, 2025

Search Tags:#kubernetes #gitops #continuous-delivery #argoCD #manifest-management #workload-onboarding #git-reviews

Ready to run

npx skills add https://github.com/buenhyden/hy-home.k8s --skill gitops-workflow-buenhyden

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gitops-workflow
Source: https://github.com/buenhyden/hy-home.k8s/tree/main/.agents/skills/gitops-workflow
Command: npx skills add https://github.com/buenhyden/hy-home.k8s --skill gitops-workflow-buenhyden

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Define the approved GitOps path for workload onboarding, change review, and ArgoCD sync diagnosis in hy-home.k8s.

Core Features & Use Cases

Define the target workload or GitOps object and confirm the repository path.
Apply or update repository-backed manifests only; do not mutate the cluster directly.
Run the validation path through k8s-validate.
Review release structure, sync targets, and rollout safety.
Move the change through PR and ArgoCD reconciliation.

Quick Start

Push the workload manifest to the repository and verify the ArgoCD sync status with a quick validation.

Frequently Asked Questions about gitops-workflow

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

FAQPage Schema

How do I onboard a workload to a Kubernetes cluster using GitOps?▼

To onboard a workload using GitOps, define the target workload and confirm the repository path, then push repository-backed manifests and verify ArgoCD sync status. This enforces deterministic reviews and versioned changes without directly mutating the cluster.

What is the approved path for GitOps change review and ArgoCD sync diagnosis?▼

The approved GitOps path involves defining targets, applying repository-backed manifests, running validation, and moving changes through PRs and ArgoCD reconciliation. This enables versioned changes and safe rollouts across environments for deterministic reviews.

Can I apply direct cluster mutations when using a GitOps workflow?▼

No, you should apply or update repository-backed manifests only and avoid mutating the cluster directly. This GitOps-first discipline ensures safe rollouts across environments via PRs and ArgoCD reconciliation.

How do I validate Kubernetes manifests before an ArgoCD sync?▼

You validate Kubernetes manifests by running the validation path through k8s-validate before moving the change through PR and ArgoCD reconciliation. This confirms release structure, sync targets, and rollout safety.

What's the best way to diagnose ArgoCD sync issues for repository-backed manifests?▼

The best way to diagnose ArgoCD sync issues is to verify the sync status after pushing the workload manifest, ensuring you review the release structure and sync targets. This confirms rollout safety and validates the repository-backed manifests.