neb-argocd-debug

Triage ArgoCD deployment issues through a structured 5-phase workflow.

Updated Aug 23, 2026

Search Tags:#devops #debugging #troubleshooting #kubernetes #kubectl #argocd

Ready to run

npx skills add https://github.com/nebinfra/nebcore-ai-skills --skill neb-argocd-debug

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic ArgoCD troubleshooting — from symptom to resolution with guardrails

Core Features & Use Cases

Guided, phase-based investigation of ArgoCD deployment issues
Interactive troubleshooting with hard guardrails to prevent destructive actions
Reproducible remediation and verification workflow across cluster contexts

Quick Start

Provide an ArgoCD issue scenario and have the assistant guide through Phase 1–5 triage and remediation steps.

Frequently Asked Questions about neb-argocd-debug

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

FAQPage Schema

How do I troubleshoot ArgoCD sync failures and OutOfSync application states?▼

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.

Why does my ArgoCD application show a degraded health status after deployment?▼

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.

What is the best way to debug ArgoCD deployment issues without causing destructive cluster changes?▼

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.

Can I use kubectl and ArgoCD CLI to resolve sync errors across multiple Kubernetes cluster contexts?▼

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.

Do I need ArgoCD CLI access to investigate Kubernetes deployment issues systematically?▼

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.

What are the limitations of interactive ArgoCD troubleshooting workflows?▼

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.