Skip to content

dirien/yet-another-agent-harness / .claude/skills/flux-cli

flux-cli

Flagged

Bootstraps Flux CD on Kubernetes clusters, creates and manages GitOps sources (Git/Helm/OCI/Bucket), configures kustomizations and Helm releases, reconciles resources, sets up image automation and alerting, and pushes OCI artifacts. Use this skill whenever the user mentions the flux CLI, flux bootstrap, flux create source, flux create kustomization, flux create helmrelease, flux reconcile, flux get, Flux CD, GitOps with Flux, or asks about managing Kubernetes deployments via GitOps. Also trigger when users ask about creating Git/Helm/OCI/Bucket sources, building or diffing kustomizations, pushing OCI artifacts, setting up image automation, creating Flux alerts/receivers, or bootstrapping Flux on GitHub/GitLab/Gitea/Bitbucket. Even if the user just says "flux" in a Kubernetes context, this skill applies.

FileKindSize
SKILL.mdskill md9.2 KB
references/artifacts-and-images.mdmarkdown6.1 KB
references/bootstrap.mdmarkdown5.6 KB
references/helmreleases.mdmarkdown4.0 KB
references/kustomizations.mdmarkdown5.5 KB
references/sources.mdmarkdown6.0 KB

references/helmreleases.md

View on GitHub
# HelmRelease Commands

HelmReleases tell Flux how to install and manage Helm charts.

---

## flux create helmrelease

```bash
flux create helmrelease <name> [flags]
```

### Flags

| Flag | Default | Description |
|------|---------|-------------|
| `--chart` | — | Helm chart name or path (required unless `--chart-ref` is set) |
| `--source` | — | Chart source: `<kind>/<name>.<namespace>`. Kind: `HelmRepository`, `GitRepository`, `Bucket` |
| `--chart-ref` | — | Reference to a HelmChart or OCIRepository: `<kind>/<name>.<namespace>` |
| `--chart-version` | — | Chart version (semver range accepted; ignored for Git sources) |
| `--chart-interval` | — | Interval to check for new chart versions |
| `--release-name` | — | Custom Helm release name (defaults to HelmRelease name) |
| `--target-namespace` | — | Namespace to install the chart into |
| `--storage-namespace` | — | Namespace for storing Helm release metadata |
| `--create-target-namespace` | `false` | Create target namespace if it doesn't exist |
| `--values` | — | Local path to values.yaml file(s) (repeatable) |
| `--values-from` | — | K8s object reference for values: `Secret/<name>` or `ConfigMap/<name>` (repeatable) |
| `--depends-on` | — | Dependencies: `<name>` or `<namespace>/<name>` (repeatable) |
| `--crds` | — | CRD upgrade policy: `Skip`, `Create`, `CreateReplace` |
| `--service-account` | — | Service account for impersonation |
| `--kubeconfig-secret-ref` | — | Secret with kubeconfig for remote cluster |
| `--reconcile-strategy` | `ChartVersion` | Strategy: `Revision` or `ChartVersion` |
| `--interval` | `1m` | Reconciliation interval |
| `--export` | — | Output YAML instead of applying |
| `--label` | — | Labels as `key=value` (repeatable) |

### Examples

```bash
# From a HelmRepository
flux create helmrelease nginx \
  --source=HelmRepository/bitnami \
  --chart=nginx \
  --chart-version=">=15.0.0" \
  --values=./nginx-values.yaml

# From a GitRepository (chart in repo)
flux create helmrelease my-app \
  --source=GitRepository/my-app \
  --chart=./charts/my-app

# From a Bucket
flux create helmrelease my-app \
  --source=Bucket/my-bucket \
  --chart=./charts/my-app

# With values from a Secret
flux create helmrelease my-app \
  --source=HelmRepository/my-charts \
  --chart=my-app \
  --values-from=Secret/my-app-values

# Multiple values files
flux create helmrelease my-app \
  --source=HelmRepository/my-charts \
  --chart=my-app \
  --values=./base-values.yaml \
  --values=./prod-values.yaml

# Custom release name and target namespace
flux create helmrelease my-app \
  --source=HelmRepository/my-charts \
  --chart=my-app \
  --release-name=my-custom-release \
  --target-namespace=apps \
  --create-target-namespace

# With dependencies
flux create helmrelease my-app \
  --source=HelmRepository/my-charts \
  --chart=my-app \
  --depends-on=cert-manager \
  --depends-on=kube-system/external-dns

# CRD handling
flux create helmrelease cert-manager \
  --source=HelmRepository/jetstack \
  --chart=cert-manager \
  --crds=CreateReplace

# Cross-namespace source reference
flux create helmrelease my-app \
  --source=HelmRepository/shared-charts.shared-ns \
  --chart=my-app

# From an OCIRepository
flux create helmrelease my-app \
  --chart-ref=OCIRepository/my-oci-source

# Export YAML
flux create helmrelease my-app \
  --source=HelmRepository/my-charts \
  --chart=my-app \
  --export > helmrelease.yaml
```

---

## flux debug helmrelease

Debug a failing HelmRelease — shows detailed status, last attempted values,
and error messages.

```bash
flux debug helmrelease <name> [-n <namespace>]
```

---

## Managing HelmReleases

```bash
# List
flux get helmreleases [-A] [-w] [--no-header]

# Filter
flux get helmreleases --status-selector ready=false
flux get helmreleases -l app=frontend

# Force reconciliation
flux reconcile helmrelease <name>

# Suspend/resume
flux suspend helmrelease <name>
flux suspend helmrelease --all
flux resume helmrelease <name>

# Export
flux export helmrelease <name>
flux export helmrelease --all > all-hr.yaml

# Delete
flux delete helmrelease <name>
```
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall