# Gitops Argocd

> Run GitOps deployments with ArgoCD - inspect applications, diff desired vs live state, deploy through git commits and PRs, sync and verify rollouts.

- Skill: `navinspire-ia/gitops-argocd` (Agent Skill)
- Install (CLI): `npx skillmds@latest add navinspire-ia/gitops-argocd`
- Raw SKILL.md: https://api.skillmd.com/api/skills/navinspire-ia/gitops-argocd/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: Navinspire-ia (https://skillmd.com/u/navinspire-ia)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/navinspire-ia/gitops-argocd

---


# GitOps / ArgoCD

## Overview

Deploy through git, not through kubectl. The git repository is the source of truth; ArgoCD reconciles it. Prefer the ArgoCD MCP server (`argocd` preset) or the `argocd` CLI when available; fall back to reading Application CRs with kubectl.

## Common commands

```bash
argocd app list
argocd app get <app>
argocd app diff <app>
argocd app history <app>
argocd app sync <app> --dry-run
kubectl get applications.argoproj.io -n argocd
kubectl describe application <app> -n argocd
```

## Workflow

1. Locate the Application: repo URL, path, target revision, destination cluster/namespace, sync policy.
2. To change what is deployed: edit the manifests/kustomize/Helm values in the git repo, commit on a branch, open a PR/MR, and let review + ArgoCD do the rest. Do not patch live resources.
3. After merge: watch sync status and health (`argocd app get`, `app wait`), then verify the workload itself (rollout status, logs).
4. For drift: `argocd app diff` first, then decide - sync (git wins) or port the live change back into git.

## Rules

- `argocd app sync` on prod apps, rollbacks, and `app delete` require `human-approval`.
- Never disable auto-sync or prune without saying so in the report.
- Never commit secrets to the GitOps repo; use sealed-secrets/external-secrets references.