Skills gitops-workflow

📦

gitops-workflow

Name: gitops-workflow
Author: wshobson

Safe ⚙️ External commands🌐 Network access

Implement GitOps Workflows

Automate Kubernetes deployments using Git as the single source of truth. Implement declarative infrastructure management with ArgoCD and Flux for reliable, auditable deployments.

Supports: Claude Codex Code(CC)

📊 70 Adequate

Download the skill ZIP

Upload in Claude

Go to Settings → Capabilities → Skills → Upload skill

Toggle on and start using

Test it

Using "gitops-workflow". Help me create an ArgoCD application for my microservice

Expected outcome:

I'll help you create an ArgoCD application. Here's a complete Application manifest:
Application configuration with:
• Git repository source pointing to your microservice
• Automated sync policy with prune and self-heal
• Health checks and sync options
• Proper namespace and destination cluster
Installation commands for kubectl
Verification steps to check deployment status

Using "gitops-workflow". Show me how to configure Flux for my GitLab repository

Expected outcome:

Here's how to set up Flux with GitLab:
Step 1: Install Flux CLI
Step 2: Configure GitLab connection credentials
Step 3: Create GitRepository manifest pointing to GitLab
Step 4: Create Kustomization for your deployment
Key configuration elements:
• Source reference pointing to GitLab repository
• Sync interval for periodic reconciliation
• Prune option for cleanup of removed resources

Using "gitops-workflow". How do I manage secrets securely in GitOps

Expected outcome:

There are several approaches for secret management in GitOps:
Option 1 - External Secrets Operator:
• Pulls secrets from AWS Secrets Manager, Azure Key Vault, or HashiCorp Vault
• Secret content never stored in Git
• Automatic refresh based on interval
Option 2 - Sealed Secrets:
• Encrypts secrets before committing to Git
• Cluster-wide decryption key required
• Useful for git-only workflows

Security Audit

Safe

v4 • 1/17/2026

Documentation-only skill containing markdown guides and YAML examples for GitOps workflows. Static analyzer flagged markdown code blocks and Lua syntax as security patterns - all are false positives. No executable code, no network calls, no file system access, no external data processing. Safe for marketplace publication.

Files scanned

754

Lines analyzed

findings

Total audits

Risk Factors

⚙️ External commands (72)

🌐 Network access (15)

references/argocd-setup.md:8 references/argocd-setup.md:13 references/argocd-setup.md:18 references/argocd-setup.md:72 references/argocd-setup.md:78 references/argocd-setup.md:80 references/argocd-setup.md:94 skill-report.json:6 SKILL.md:39 SKILL.md:79 SKILL.md:83 SKILL.md:104 SKILL.md:108 SKILL.md:120 SKILL.md:141

Audited by: claude View Audit History →

Quality Score

Architecture

100

Maintainability

Content

Community

100

Security

Spec Compliance

What You Can Build

Set up GitOps pipelines

Configure ArgoCD or Flux to automatically deploy applications from Git repositories to Kubernetes clusters.

Standardize deployments

Implement consistent deployment patterns across multiple teams and environments using GitOps principles.

Enable declarative infrastructure

Manage Kubernetes infrastructure declaratively with version control, rollback capabilities, and audit trails.

Try These Prompts

Basic ArgoCD setup

Help me install ArgoCD on my Kubernetes cluster and create my first application that deploys from a Git repository.

Flux bootstrap

Show me how to bootstrap Flux CD connected to my GitHub repository and create a Kustomization for my app.

Progressive delivery

I need to set up canary deployments with ArgoCD Rollouts. Show me the configuration and steps.

Multi-cluster management

How do I use the App of Apps pattern to manage multiple applications across different Kubernetes clusters?

Best Practices

Use separate Git repositories or branches for different environments to isolate changes
Enable automated sync only for development and staging environments
Implement health checks for custom resources to ensure proper deployment status visibility

Avoid

Storing plain text secrets in Git repositories creates security vulnerabilities
Using automated sync for production without approval gates risks uncontrolled deployments
Mixing infrastructure and application code in the same repository complicates access control

Frequently Asked Questions

Which GitOps tool should I choose - ArgoCD or Flux?

ArgoCD has a rich UI and is easier for beginners. Flux is more lightweight and integrates well with GitHub. Both follow GitOps principles.

Can I use this with private Git repositories?

Yes, both tools support private repositories through SSH keys or access tokens. Configure credentials during setup.

How do I handle secrets in GitOps?

Use External Secrets Operator to pull from secret managers, or Sealed Secrets to encrypt secrets before committing to Git.

What happens if the Git repository is unavailable?

GitOps tools cache the last known state. Applications continue running, but new deployments require Git accessibility.

Can I rollback deployments?

Yes, by reverting to a previous Git commit. GitOps tools automatically sync the cluster to match the desired state.

How do I monitor sync status?

Use ArgoCD UI or Flux CLI commands. Set up Prometheus alerts for failures and configure notifications to Slack or email.

Developer Details

Author

wshobson

License

MIT

Repository

https://github.com/wshobson/agents/tree/main/plugins/kubernetes-operations/skills/gitops-workflow

Ref

main

File structure

📁 references/

📄 argocd-setup.md

📄 sync-policies.md

📄 SKILL.md