Menu
Systematically investigate cluster issues starting from events, following the Flux pipeline down to pod logs
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Enforces staged execution discipline on large tasks: a written stage plan, delegation to named fable agents where the runtime supports it, a failable verification check at each stage, and a skeptical self-review before delivery. Trigger when the user explicitly asks ("do this thoroughly", "be systematic", "deep work mode") OR when the task objectively spans multiple files, multiple sources, or multiple sessions. Do NOT trigger on ordinary multi-step requests that a direct attempt handles fine. For a run pinned to a specific model, use fable-opus, fable-sonnet, or fable-haiku instead. Always-on guardrails (verify-before-flag, warning batching, sed safety) live in the companion execution-guardrails skill.
Run Kopiur S3 backups alongside VolSync NFS, verify over days, then cutover with full restore from S3
Migrate an app's PVC backup from VolSync to Kopiur with zero data loss
Scaffold a new app-template application for this home-ops repository
Analyze GitOps repo structure for ordering issues, broken references, missing dependencies, and anti-patterns
Safely upgrade an app's image or chart version, checking for breaking changes and updating the HelmRelease
| name | cluster-debug |
| description | Systematically investigate cluster issues starting from events, following the Flux pipeline down to pod logs |
| argument-hint | [namespace/app or issue description] - Optional focus area |
MISSION: Investigate cluster state using read-only operations, identify root causes, and propose GitOps-based fixes.
SCOPE: $ARGUMENTS
If no arguments provided, perform a full cluster health check.
kubectl get events -A --sort-by='.lastTimestamp' | grep -v Normal | tail -30
flux get ks -A | grep -v "True"
flux get hr -A | grep -v "True"
For a specific app:
flux logs --kind=HelmRelease --namespace=<ns> --name=<app> --since=1h
kubectl get pods -n <ns> -o wide
kubectl describe pod -n <ns> <pod>
kubectl logs -n <ns> <pod> --previous # if crashlooping
kubectl logs -n <ns> <pod> -f # live
flux reconcile kustomization flux-system --with-source
flux reconcile hr <name> -n <namespace> --force
kustomize build kubernetes/apps/<namespace>/<app>/app
kubectl logs --previous for the actual errorreadOnlyRootFilesystem: true — app may need a writable path in tmpfskubectl describe pod → Events sectionexistingClaim name matches actual PVCbypathMode issuestrategy: Recreatekubectl get externalsecret -n <ns> <name> -o jsonpath='{.status.conditions}'
kubectl get secret -n <ns> <name>
kubectl apply/patch/delete for persistent changes — edit Git sourcedisable-<app> Flux KS without explicit instruction