Triage ArgoCD deployment issues through a structured 5-phase workflow.
npx skills add https://github.com/nebinfra/nebcore-ai-skills --skill neb-argocd-debug
Please help me install this Agent Skill. Skill: neb-argocd-debug Source: https://github.com/nebinfra/nebcore-ai-skills/tree/main/neb-argocd-debug Command: npx skills add https://github.com/nebinfra/nebcore-ai-skills --skill neb-argocd-debug
Systematic ArgoCD troubleshooting — from symptom to resolution with guardrails
Provide an ArgoCD issue scenario and have the assistant guide through Phase 1–5 triage and remediation steps.
High-intent search queries and answers about installing and using this skill.
ArgoCD sync failures are troubleshooted using a structured 5-phase workflow that guides interactive investigation from symptom identification to remediation. This process requires kubectl and ArgoCD CLI access to triage deployment issues across Kubernetes cluster contexts.
ArgoCD health failures are investigated by triaging symptoms through phase-based analysis using kubectl and ArgoCD CLI. The structured workflow identifies root causes during the investigation phase and applies guarded remediation steps to resolve the degraded status.
Debugging ArgoCD deployment issues safely requires a workflow with hard guardrails that prevent destructive actions during triage and remediation. This structured approach ensures reproducible investigation and verification across Kubernetes cluster contexts without risking infrastructure.
Yes, resolving ArgoCD sync errors across multiple Kubernetes cluster contexts requires kubectl and ArgoCD CLI access. The structured 5-phase workflow supports interactive investigation, remediation, and verification reproducibly across different cluster contexts.
Yes, ArgoCD CLI access is required alongside kubectl to perform systematic troubleshooting of ArgoCD deployment issues. The 5-phase workflow depends on both tools to triage symptoms, investigate failures, apply remediation, and verify resolution across Kubernetes clusters.
The troubleshooting workflow is limited to interactive investigations of ArgoCD sync and health failures, requiring active kubectl and ArgoCD CLI access. It enforces hard guardrails to prevent destructive actions, meaning fully automated or unsupervised remediation is not supported.
phuetzConsolidate kubectl, Helm, and ArgoCD workflows for Kubernetes cluster administration.
alexmarucciAutomate incident detection, tracking, escalation, resolution, and post-mortem analysis via Datadog API.
cnoe-ioAnalyze ArgoCD application sync and health statuses across clusters.
BagelHoleDefine ArgoCD applications, projects, and sync policies for GitOps deployments.
