argocd

ArgoCD GitOps continuous delivery for Kubernetes. Use for K8s GitOps.

7 stars

byG1Joshi

View on GitHub Installation ↓

Best use case

argocd is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

ArgoCD GitOps continuous delivery for Kubernetes. Use for K8s GitOps.

Teams using argocd should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/argocd/SKILL.md --create-dirs "https://raw.githubusercontent.com/G1Joshi/Agent-Skills/main/skills/devops/argocd/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/argocd/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How argocd Compares

Feature / Agent	argocd	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

ArgoCD GitOps continuous delivery for Kubernetes. Use for K8s GitOps.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# ArgoCD

ArgoCD is the industry standard for **GitOps**. It syncs the state of a Kubernetes cluster with a Git repository. 2025 features: **ApplicationSets** for multi-tenant management.

## When to Use

- **Kubernetes CD**: Continuous Delivery specifically for K8s.
- **GitOps**: You want your cluster state (YAML) versioned in Git.
- **Drift Detection**: ArgoCD alerts you if someone manually hacks `kubectl edit` in production.

## Quick Start

```yaml
# Application.yaml
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: guestbook
  namespace: argocd
spec:
  project: default
  source:
    repoURL: https://github.com/argoproj/argocd-example-apps.git
    targetRevision: HEAD
    path: guestbook
  destination:
    server: https://kubernetes.default.svc
    namespace: guestbook
```

## Core Concepts

### Application

The link between a Git source and a K8s destination.

### ApplicationSet

A generator that spawns multiple `Application` resources. Example: "Deploy _every_ folder in this repo as an app" or "Deploy this app to _every_ cluster".

### Sync Phases

Pre-Sync (Schema migration), Sync (Deployment), Post-Sync (Health check).

## Best Practices (2025)

**Do**:

- **Use ApplicationSets**: The modern way to manage many apps.
- **Separate Config from Code**: Keep app source code and K8s manifests in separate repos or at least separate folders.
- **Use "App of Apps"**: A bootstrap pattern where one root Argo app deploys all other apps.

**Don't**:

- **Don't manage Secrets in plain Git**: Use Sealed Secrets, External Secrets Operator, or ArgoCD Vault Plugin.

## References

- [ArgoCD Documentation](https://argo-cd.readthedocs.io/)