gitops

Diagnose Argo CD and Flux reconciliation drift and gate GitOps mutations safely.

Updated May 11, 2026
One-click install
npx skills add https://github.com/cloudofgeorge/AI-hands-Engineer --skill gitops-cloudofgeorge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitops
Source: https://github.com/cloudofgeorge/AI-hands-Engineer/tree/main/skills/engineering/domains/infrastructure/gitops
Command: npx skills add https://github.com/cloudofgeorge/AI-hands-Engineer --skill gitops-cloudofgeorge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? GitOps controllers like Argo CD and Flux continuously reconcile live Kubernetes clusters against Git, and a careless sync, prune, or manual kubectl edit can delete resources, conceal drift, or bypass review. This Skill provides a safety-first triage workflow for investigating reconciliation issues before any live mutation. ## Core Features & Use Cases - Read-only diagnosis: Inspect desired vs. live revisions, sync status, controller conditions, events, and diffs using argocd app get/diff and flux get commands before acting. - Divergence triage: Structured guidance for OutOfSync drift, degraded resources, source fetch failures, reconciliation loops, and unexpected deletions. - Approval gate for mutations: A required checklist covering target, evidence, risk, change, verification, and recovery before any sync, reconcile, rollback, or prune. - Use Case: An application shows OutOfSync in Argo CD. Use this Skill to compare the immutable desired revision against live state, identify whether drift came from a manual edit, and prepare an evidence-backed approval request before syncing. ## Quick Start Use the gitops skill to investigate why my Argo CD application is OutOfSync and tell me whether it is safe to sync.

Frequently Asked Questions about gitops

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

FAQPage Schema
How do I troubleshoot an OutOfSync application in Argo CD?

Start read-only: run argocd app get, app history, and app diff to compare the desired immutable Git revision against live state. Identify whether drift came from manual edits or controller-owned differences before considering any sync.

How do I check Flux reconciliation status for a Kustomization or HelmRelease?

Run flux check, then flux get sources, kustomizations, and helmreleases scoped to the confirmed namespace. Inspect observed generation, last applied revision, conditions, events, and narrowly scoped controller logs to locate the failing layer.

Is flux reconcile a read-only diagnostic command?

No. flux reconcile asks the controller to reconcile and can apply the current desired state to the cluster. Treat it as a mutation requiring explicit confirmation, not as a diagnostic inspection.

Should I use kubectl to manually fix a GitOps-managed resource?

No. Manual kubectl edits create drift and may be overwritten by the controller, concealing the real problem. Fix the reviewed desired state in Git or explicitly accept a known controller-owned difference.

What should I check before rolling back a GitOps deployment?

Prefer a reviewed Git revert or documented controller rollback to a known immutable revision. Re-render and review the resulting diff, since an old revision may not be safe for current data, schemas, or dependencies, and obtain approval again.