gitops-argocd

Manages ArgoCD GitOps workflows for syncing Kubernetes manifests and WorkflowTemplates from git.

11|9|Updated May 25, 2026
One-click install
npx skills add https://github.com/projectbluefin/lab --skill gitops-argocd-projectbluefin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gitops-argocd
Source: https://github.com/projectbluefin/lab/tree/main/docs/skills/gitops-argocd
Command: npx skills add https://github.com/projectbluefin/lab --skill gitops-argocd-projectbluefin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents configuration drift and failed deployments in an ArgoCD-managed Kubernetes lab by defining exactly which git paths ArgoCD owns, how sync and self-heal behave, and how to verify changes actually reached the live cluster before running workflows. ## Core Features & Use Cases - Application ownership map: Documents which ArgoCD Applications manage which git paths (workflow-templates, manifests, bootstrap) so new files land in the right place. - Sync troubleshooting: Diagnoses OutOfSync states, repo-specific reconciliation stalls, Server-Side Apply pitfalls, and the WorkflowTemplate snapshot race condition. - Verification protocol: Enforces a four-step check (git push, ArgoCD sync, live template inspection, then workflow submission) before declaring a fix deployed. - Use Case: You edited a WorkflowTemplate, pushed to main, but the cluster still runs the old version. This Skill walks you through forcing a hard refresh, confirming the live template content, and only then submitting a new workflow. ## Quick Start Ask the assistant to check whether my ArgoCD Applications are synced and why my pushed WorkflowTemplate change is not live in the cluster.

Frequently Asked Questions about gitops-argocd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I force an ArgoCD Application sync from the command line?▼

Run argocd app sync <name> --timeout 120, or trigger a hard refresh without the CLI using kubectl patch app <name> -n argocd with the argocd.argoproj.io/refresh=hard annotation. Verify status afterward with argocd app get.

Why did ArgoCD revert my manual kubectl apply change?▼

ArgoCD reverts manual changes because the Application uses automated sync with selfHeal: true, which restores git state within about three minutes. Commit the change to git on the tracked branch instead of applying it directly.

Why is my WorkflowTemplate change in git but not live in the cluster?▼

ArgoCD polls or receives webhooks on a delay, and WorkflowTemplates are snapshotted at workflow submit time. Force a hard refresh, confirm the Application is Synced, and inspect the live template before submitting any workflow.

Can I use generateName in ArgoCD-managed manifests with Server-Side Apply?▼

No, generateName is forbidden in manifests managed with ServerSideApply because ArgoCD needs stable names to track resources. Always declare a fixed metadata.name so SSA can patch the object in place.

What causes an ArgoCD repo-specific reconciliation stall?▼

A stall is repo-specific when Applications tracking one repository stay pinned to an old commit while Applications tracking other repos update normally. Compare REVISION across Applications and confirm the stuck revision with git log before forcing a resync.

When should I suspend a CronWorkflow instead of deleting it?▼

Suspend a CronWorkflow in git with spec.suspend: true when it is temporarily broken, such as a blocked upstream image. Delete the manifest only when it is permanently abandoned, since ArgoCD prune removes the resource from the cluster.