gitops-apply

Guide Kubernetes resource changes through declarative Git manifests and ArgoCD or Flux sync.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/meriley/claude-code-skills --skill gitops-apply
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitops-apply
Source: https://github.com/meriley/claude-code-skills/tree/main/skills/gitops-apply
Command: npx skills add https://github.com/meriley/claude-code-skills --skill gitops-apply

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill guides users away from direct kubectl mutations, enforcing a declarative GitOps workflow for Kubernetes resource management, ensuring auditability, reviewability, and recoverability.

Core Features & Use Cases

  • Enforces GitOps: Replaces imperative kubectl commands with declarative manifest changes in Git.
  • Workflow Guidance: Provides step-by-step instructions for locating, editing, committing, and syncing Kubernetes manifests.
  • Bootstrap Exception Handling: Details a specific workflow for bootstrapping ArgoCD itself, which cannot be managed by GitOps.
  • Use Case: When a user attempts to scale a deployment directly using kubectl scale deployment..., this skill intervenes and guides them through updating the deployment manifest in Git and letting ArgoCD/Flux handle the sync.

Quick Start

Use the gitops-apply skill to update the image tag for the 'api-service' deployment in the 'production' namespace.

Frequently Asked Questions about gitops-apply

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

FAQPage Schema
How do I update Kubernetes resources without using imperative kubectl commands?

GitOps replaces direct kubectl mutations by guiding you to update manifests in Git and letting ArgoCD or Flux sync the changes. This ensures operations are auditable, reviewable, and recoverable through commit history.

What is the GitOps workflow for managing Kubernetes deployments?

The GitOps workflow for Kubernetes involves identifying target resources, locating their manifests in Git, editing the files, committing changes using conventional commits, and allowing ArgoCD or Flux to automatically sync the updates to the cluster.

Can I bootstrap ArgoCD using the declarative GitOps workflow?

You cannot bootstrap ArgoCD using the standard declarative GitOps workflow because it cannot manage itself. A specific bootstrap exception handling process is required to set up ArgoCD initially before it can manage other resources.

Why should I scale a Kubernetes deployment via Git instead of kubectl scale?

Scaling via Git instead of kubectl scale enforces declarative GitOps, ensuring changes are auditable and recoverable. You update the deployment manifest in Git and let ArgoCD or Flux handle the synchronization automatically.

Does the GitOps workflow support both Flux and ArgoCD for syncing Kubernetes manifests?

Yes, the GitOps workflow supports syncing Kubernetes manifests through both ArgoCD and Flux. After you locate, edit, and commit manifest changes to Git, either tool can automatically synchronize the desired state to your cluster.