Gitops

Use when the user asks about GitOps, Flux, Git as the source of truth, drift detection, multi-environment promotion, Kustomize overlays, secrets in GitOps, or how to sync cluster state from git with Argo CD or Flux. Produces GitOps repo layouts and promotion flows. Not for Argo CD specifics (use argo-cd) or ApplicationSets at scale (use devops-gitops-advanced).

45 stars 6 forksDevOps & Cloud

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add j4flmao/agent-skills --skill gitops
Manual install
git clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/devops/gitops ~/.claude/skills/gitops

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# GitOps

## Purpose
Manage Kubernetes deployments using Git as the single source of truth with ArgoCD or Flux. Covers repository structure, application definitions, sync policies, environment promotion, drift detection, and secret management.

## Framework and Methodology

### GitOps Principles
1. Declarative Description: The entire system is described declaratively.
2. Version Controlled and Immutable: The desired state is stored in Git.
3. Automatically Applied: Software agents pull changes from Git.
4. Continuously Reconciled: Agents correct drift between desired and actual state.

### Reconciliation Loop
```
Git (desired state) -> GitOps Controller watches repo
  -> Compares with cluster state
  -> Detects drift (manual change or config divergence)
  -> Applies desired state to cluster
  -> Reports sync status
  -> Loops continuously (default every 3-5 minutes)
```

### Pull vs Push Model
Pull-based (GitOps native): Agent in cluster pulls from Git. Cluster initiates all changes. No external access to cluster API needed. More secure.

Push-based (CI/CD traditional): CI system pushes to cluster. Cluster API exposed to CI system. Higher blast radius (CI compromise = cluster compromise).

Recommendation: Always use pull-based for production.

## Agent Protocol

### Trigger
Exact user phrases: "GitOps", "ArgoCD", "Flux", "Git as source of truth", "sync policy", "drift detection", "Application CRD", "sync waves".

### Input Context
- GitOps tool (ArgoCD vs Flux).
Read the full skill on GitHub

Details

Skill name
gitops
Path
skills/devops/gitops/SKILL.md
License
MIT
Repo updated
17 November 2026

FAQ

What does the Gitops skill do?

Use when the user asks about GitOps, Flux, Git as the source of truth, drift detection, multi-environment promotion, Kustomize overlays, secrets in GitOps, or how to sync cluster state from git with Argo CD or Flux. Produces GitOps repo layouts and promotion flows. Not for Argo CD specifics (use argo-cd) or ApplicationSets at scale (use devops-gitops-advanced).

How do I install the Gitops skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill gitops. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Gitops popular?

It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.

Related skills

Agent Observability

45

j4flmao/agent-skills

Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).

DevOps & Cloud

AI Agent Architectures

45

j4flmao/agent-skills

Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).

AI, LLMs & Agents

AI Agent Core Loop

45

j4flmao/agent-skills

Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).

AI, LLMs & Agents

Helm Patterns

45

j4flmao/agent-skills

Use when the user asks to package an app as a Helm chart, Helm values per environment, helm upgrade or rollback, helmfile, chart dependencies and subcharts, library charts, helm unittest, OCI chart registries, or helm diff. Produces charts and release workflows. Not for a chart plus operator scaffold (use cloud-native-kubernetes-mastery) or GitOps sync (use argo-cd).

DevOps & Cloud

Github Actions

45

j4flmao/agent-skills

Use when the user asks for a GitHub Actions workflow to test and deploy on push, reusable workflows, composite actions, matrix builds, GITHUB_TOKEN permissions, OIDC to a cloud, self-hosted runners, or caching. Produces secure workflow YAML with pinned actions. Not for vendor-neutral pipeline design (use cicd-pipeline) or GitLab CI (use devops-gitlab-ci).

DevOps & Cloud

Hetzner Cloud

45

j4flmao/agent-skills

Use when the user asks about Hetzner Cloud, the hcloud CLI, Hetzner dedicated servers or Robot, the server auction, CX/CPX/CAX/CCX types, Storage Box, vSwitch, Hetzner firewalls or load balancers, or Kubernetes on Hetzner. Produces Hetzner infrastructure with Terraform or Packer. Not for DigitalOcean (use digitalocean) or PXE provisioning (use bare-metal).

DevOps & Cloud

Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.