gitops

GitOps workflows for this repo: edit Argo CD/Kubernetes/infra manifests in version control, validate changes, and rely on Argo CD to sync. Use when tasks touch argocd/, kubernetes/, tofu/, ansible/, or deployment/runbook changes, or when asked to roll out services via GitOps.

⭐4stars🔀0forks📁View on GitHub🕐Updated Jan 9, 2026

When & Why to Use This Skill

This Claude skill automates GitOps workflows by managing Argo CD, Kubernetes, and Infrastructure as Code (IaC) manifests. It streamlines the deployment process through version control, ensuring that all infrastructure changes are validated via linting and planning tools before being reconciled by Argo CD. By enforcing a 'Git-as-the-source-of-truth' approach, it enhances deployment reliability, security, and traceability while minimizing manual cluster interventions.

Use Cases

  • Automated Service Rollouts: Managing the end-to-end lifecycle of service deployments by updating Argo CD applications and monitoring sync status until the environment is healthy.
  • Infrastructure as Code (IaC) Management: Editing and validating Tofu/Terraform manifests and Ansible playbooks to maintain consistent cloud infrastructure states.
  • Pre-deployment Validation: Running local guardrails such as Argo lint, Kubeconform, and Terraform plans to catch configuration errors before they reach production.
  • Kubernetes Manifest Orchestration: Updating K8s overlays and resource definitions within version control to ensure declarative state alignment across different environments.
  • Emergency Cluster Recovery: Providing a structured workflow for manual kubectl interventions during emergencies while maintaining documentation and Git synchronization.
namegitops
description"GitOps workflows for this repo: edit Argo CD/Kubernetes/infra manifests in version control, validate changes, and rely on Argo CD to sync. Use when tasks touch argocd/, kubernetes/, tofu/, ansible/, or deployment/runbook changes, or when asked to roll out services via GitOps."

GitOps

Overview

Use GitOps-first changes for infra and deployment workflows, then validate locally and let Argo CD reconcile. Only apply directly to the cluster when explicitly instructed or in an emergency.

Workflow

  1. Locate the source of truth

    • Argo CD apps and overlays: argocd/
    • Kubernetes manifests: kubernetes/
    • IaC: tofu/, ansible/
    • Service-specific instructions: nearest README.md
  2. Edit manifests in Git

    • Prefer updating Argo CD apps/overlays instead of raw kubectl applies.
    • Keep environment-specific changes in overlays.
  3. Validate locally

    • Argo lint: scripts/argo-lint.sh
    • Kubeconform: scripts/kubeconform.sh argocd
    • Terraform/tofu: bun run tf:plan (apply only when asked)
    • Ansible: bun run ansible
  4. Rollout discipline

  • Note rollout/impact for changes in argocd/, kubernetes/, tofu/, ansible/.
  • For Helm charts with kustomize, use: mise exec helm@3 -- kustomize build --enable-helm <path>.
  1. Cluster access (exception-only)
  • Use direct kubectl apply only when explicitly asked or in emergencies.
  • Always set namespace: kubectl ... -n <ns>.
  1. Deploy completion guardrail
    • Only call a deploy "completed" after the Argo CD application is synced and healthy.

Pointers

  • Use references/gitops-checklist.md for quick commands and repo-specific notes.