skills.rest
charchess
charchessCOMMUNITY
Explore all skills by this author →
GitHub

vixens-argocd-safety

Provide safety rules and procedures for operating ArgoCD clusters.

1|Updated Aug 29, 2025
Search Tags:#troubleshooting#safety#kubernetes#gitops#argocd#incident prevention
One-click install
npx skills add https://github.com/charchess/vixens --skill vixens-argocd-safety
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vixens-argocd-safety
Source: https://github.com/charchess/vixens/tree/main/.opencode/skills/vixens-argocd-safety
Command: npx skills add https://github.com/charchess/vixens --skill vixens-argocd-safety

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents catastrophic failures in ArgoCD deployments by providing strict, safety-critical rules and procedures to follow before and during sensitive operations.

Core Features & Use Cases

  • Incident Prevention: Details lessons learned from a major cluster failure caused by incorrect ArgoCD operations.
  • Safe Procedures: Outlines mandatory "ALWAYS DO" steps and "NEVER DO" prohibitions for ArgoCD troubleshooting and updates.
  • Use Case: Before performing any sync, refresh, or restart operation on ArgoCD, especially in production, consult this Skill to ensure you follow the correct, safe sequence of diagnostic and remedial actions, avoiding common pitfalls like branch/tag conflicts or repo-server issues.

Quick Start

Always review the ArgoCD safety rules before touching ArgoCD apps in production.

Frequently Asked Questions about vixens-argocd-safety

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

FAQPage Schema
How do I prevent catastrophic cluster failures when syncing ArgoCD applications?▼

To prevent ArgoCD cluster failures, follow strict safety rules and mandatory diagnostic steps before executing sensitive sync or refresh operations in production. Adhering to these procedures avoids common pitfalls like branch and tag conflicts.

What are the most common ArgoCD troubleshooting pitfalls involving repo-server health?▼

Common ArgoCD troubleshooting pitfalls involve ignoring repo-server health issues and branch versus tag conflicts. Addressing these specific areas during diagnostics prevents cascading cluster failures during GitOps operations.

What is the correct step-by-step procedure for a safe ArgoCD refresh?▼

A safe ArgoCD refresh requires following a strict step-by-step procedure that includes checking repo-server health and resolving branch or tag conflicts before executing the operation. This prevents catastrophic cluster failures.

Can I restart ArgoCD applications in production without causing GitOps incidents?▼

You can restart ArgoCD applications safely by adhering to hard prohibitions and mandatory diagnostic steps. Never restart without verifying repo-server health and resolving branch conflicts first to avoid incidents.

Why do branch and tag conflicts cause ArgoCD sync failures?▼

Branch and tag conflicts cause ArgoCD sync failures by creating discrepancies between the desired Git state and the deployed cluster state. Safety rules mandate resolving these conflicts before operations to prevent failures.

Related Skills

Explore More Software Engineering Skills→
voidrotvoidrot

gitops-workflow

Automate Kubernetes deployments with GitOps using ArgoCD or Flux CD.

Community
Advanced
kcns008kcns008
5

gitops

Manage GitOps deployment workflows for Kubernetes and OpenShift applications.

Community
Advanced
charchesscharchess
1

vixens-cluster

Operate Vixens Kubernetes clusters with kubectl, talosctl, and ArgoCD commands.

Community
Advanced
ivegamsftivegamsft

gitops

Implement GitOps practices for Kubernetes with Flux and ArgoCD.

Community
Advanced