skills/argocd-command-skill/SKILL.md
ArgoCD CLI interaction for cafehyna-hub cluster. USE WHEN managing ArgoCD applications OR applicationsets OR syncing OR deploying OR checking app status OR managing clusters/repos/projects via argocd CLI at argocd.cafehyna.com.br or localhost:8080.
npx skillsauth add julianobarbosa/claude-code-skills ArgoCdCommandInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Complete ArgoCD CLI interaction skill for the cafehyna-hub cluster at argocd.cafehyna.com.br or via port-forward at localhost:8080.
| Setting | Value |
|---------|-------|
| Kubeconfig | ~/.kube/aks-rg-hypera-cafehyna-hub-config |
| ArgoCD Server | argocd.cafehyna.com.br |
| ArgoCD Namespace | argocd |
| Port-Forward | localhost:8080 |
# Set kubeconfig for cafehyna-hub
export KUBECONFIG=~/.kube/aks-rg-hypera-cafehyna-hub-config
# Or use --kubeconfig flag
kubectl --kubeconfig ~/.kube/aks-rg-hypera-cafehyna-hub-config get pods -n argocd
# Add to ~/.bashrc or ~/.zshrc
alias k-hub='kubectl --kubeconfig ~/.kube/aks-rg-hypera-cafehyna-hub-config'
alias argocd-hub='KUBECONFIG=~/.kube/aks-rg-hypera-cafehyna-hub-config argocd'
| Mode | Server | Use Case |
|------|--------|----------|
| Production | argocd.cafehyna.com.br | Direct access to ArgoCD |
| Port-Forward | localhost:8080 | Local development/debugging |
| Workflow | Trigger | File |
|----------|---------|------|
| Login | "login to argocd", "authenticate" | Workflows/Login.md |
| AppManage | "create app", "delete app", "sync app", "app status" | Workflows/AppManage.md |
| AppSetManage | "create applicationset", "appset", "generate apps" | Workflows/AppSetManage.md |
| ClusterManage | "add cluster", "list clusters", "remove cluster" | Workflows/ClusterManage.md |
| RepoManage | "add repo", "list repos", "remove repository" | Workflows/RepoManage.md |
| ProjectManage | "create project", "list projects", "project settings" | Workflows/ProjectManage.md |
| Troubleshoot | "app logs", "diff", "rollback", "history" | Workflows/Troubleshoot.md |
# Login to production (with kubeconfig set)
export KUBECONFIG=~/.kube/aks-rg-hypera-cafehyna-hub-config
argocd login argocd.cafehyna.com.br --sso
# Login via port-forward
kubectl --kubeconfig ~/.kube/aks-rg-hypera-cafehyna-hub-config port-forward svc/argocd-server -n argocd 8080:443 &
argocd login localhost:8080 --insecure
# List applications
argocd app list
# Sync application
argocd app sync <app-name>
# Get app details
argocd app get <app-name>
# List applicationsets
argocd appset list
# Get ArgoCD pods
kubectl --kubeconfig ~/.kube/aks-rg-hypera-cafehyna-hub-config get pods -n argocd
# Get applications (CRD)
kubectl --kubeconfig ~/.kube/aks-rg-hypera-cafehyna-hub-config get applications -n argocd
# Get applicationsets (CRD)
kubectl --kubeconfig ~/.kube/aks-rg-hypera-cafehyna-hub-config get applicationsets -n argocd
# Get ArgoCD server logs
kubectl --kubeconfig ~/.kube/aks-rg-hypera-cafehyna-hub-config logs -n argocd -l app.kubernetes.io/name=argocd-server -f
| Tool | Purpose | File |
|------|---------|------|
| ArgoCdCli | Execute argocd commands with connection handling | Tools/ArgoCdCli.ts |
Example 1: Sync an application
User: "Sync the grafana application in ArgoCD"
→ Invokes AppManage workflow
→ Runs: argocd app sync grafana
→ Reports sync status and health
Example 2: Create ApplicationSet
User: "Create an applicationset for the monitoring stack"
→ Invokes AppSetManage workflow
→ Guides through appset creation with multi-source pattern
→ Applies via: argocd appset create -f appset.yaml
Example 3: Check application logs
User: "Show me logs for the failing defectdojo app"
→ Invokes Troubleshoot workflow
→ Runs: argocd app logs defectdojo --follow
→ Displays pod logs for debugging
Example 4: Add new cluster
User: "Register the new dev cluster with ArgoCD"
→ Invokes ClusterManage workflow
→ Runs: argocd cluster add <context-name>
→ Confirms cluster registration
development
End-to-end branch delivery: commit (no AI attribution) → push → open a pull request → ensure a Board work item exists (create one per task, assigned to the configured user, if none) and link it → after merge, clean up branch and worktree. Auto-detects the platform from the remote — Azure Repos + Boards (azure-devops-node-api SDK; OAuth Bearer push fallback via `az`) or GitHub (Octokit; `gh` for auth). Scripts are TypeScript, run via `bun`. Use whenever asked to "ship", "ship it", "ship this branch", "open a PR", "push and open a PR", "raise a PR", "deliver this", "send this for review", or "create a PR and link the work item" — and when a direct push to main is blocked and the change needs to go through a PR instead.
testing
Brief description of what this skill does. Include specific triggers - when should Claude use this skill? Example triggers, file types, or keywords that indicate this skill applies.
tools
Manage and troubleshoot PATH configuration in zsh. Use when adding tools to PATH (bun, nvm, Python venv, cargo, go), diagnosing "command not found" errors, validating PATH entries, or organizing shell configuration in .zshrc and .zshrc.local files.
tools
Zabbix monitoring system automation via API and Python. Use when: (1) Managing hosts, templates, items, triggers, or host groups, (2) Automating monitoring configuration, (3) Sending data via Zabbix trapper/sender, (4) Querying historical data or events, (5) Bulk operations on Zabbix objects, (6) Maintenance window management, (7) User/permission management