Claude Skill

gitops-argocd

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

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download navinspire-ia-navin-navin_skills_gitops-argocd-e9c73a3.zip · 0 KB

navinspire-ia/navin 31 4 forks AGPL-3.0 Updated 4d ago

Part of navinspire-ia/navin — 182 skills

Install

skills CLI npx skills add https://github.com/Navinspire-ia/navin/tree/main/navin/skills/gitops-argocd

Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install navinspire-ia-navin@llmmart

Git git clone https://github.com/Navinspire-ia/navin.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole navinspire-ia/navin collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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

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

Locate the Application: repo URL, path, target revision, destination cluster/namespace, sync policy.
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.
After merge: watch sync status and health (argocd app get, app wait), then verify the workload itself (rollout status, logs).
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.

Files (navin)

SKILL.md 1.5 KB

---
name: gitops-argocd
description: Run GitOps deployments with ArgoCD - inspect applications, diff desired vs live state, deploy through git commits and PRs, sync and verify rollouts.
metadata: {"navin":{"emoji":"🚀","category":"devops"}}
---

# 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.