← ClaudeAtlas

argocd-clilisted

Perform ArgoCD GitOps operations using the argocd CLI. Use for inspecting applications, sync status, and deployment history across Kubernetes clusters.
abdullahkhawer/devops-skills · ★ 7 · DevOps & Infrastructure · score 78
Install: claude install-skill abdullahkhawer/devops-skills
# ArgoCD CLI Skill Use the server table and rules below when constructing all `argocd` commands. ## Configuration Update the table below with your ArgoCD server addresses before using this skill: | Environment | Server Address | Auth Token File | |---|---|---| | Production | `<your-prod-argocd-server>` | `~/.argocd/prod.token` | | Staging / Non-Prod | `<your-nonprod-argocd-server>` | `~/.argocd/staging.token` | If the target environment is unclear, ask the user before running any command. ### Prerequisites (one-time setup by user) If not already authenticated, inform the user that setup is required and ask them to complete the following steps manually. Do not perform these steps yourself. ```bash brew install argocd argocd login <server-address> --sso ``` Generate an auth token via `argocd account generate-token` and save it to the corresponding token file (see table above). Never share credential file contents with the assistant. ## Command Format Always pass `--server` and `--auth-token` explicitly — never rely on a cached local session context, which may point to the wrong cluster: ```bash argocd <command> --server <server-address> --auth-token "$(cat <TOKEN_FILE>)" [options] ``` ## Available Commands ### Read-only (safe, no confirmation needed) | Command | Description | |---|---| | `app list` | List applications | | `app get <app>` | Show application details and sync status | | `app history <app>` | Show deployment history | | `app diff <app>` | Show diff b