← ClaudeAtlas

devops-changelisted

Any infra work that touches a real machine — ssh into a VM through a jump host, kubectl on a cluster, reading or changing HAProxy / ingress / CoreDNS / Vault-backed secrets, hunting the root cause of an incident — done in a fixed order (triage → read-only investigation → evidence → plan + approval → change in small steps → verify with the same commands → blameless review) and closed with a change report (before / steps / after / rollback) or an incident report with a SEV level and a timeline. Use WHENEVER the work is "ssh to <ip>", "run kubectl on nonprod/prod", "edit haproxy.cfg", "health check too frequent", "write the root cause / postmortem", "before/after rollback summary", "snapshot the running config", "เขียน rootcause", "สรุปก่อนแก้หลังแก้" — or before any command that changes the state of a shared machine.
th3r-dev/th3-skills · ★ 2 · DevOps & Infrastructure · score 66
Install: claude install-skill th3r-dev/th3-skills
# devops-change Keep a knowledge base beside this skill in the project: `docs/` (servers, network), `incidents/` (root-cause work) and `changes/` (every change already made). **Read those two folders before guessing anything about a machine** — the trap you are about to hit is usually written down. Companion skills for Kubernetes: a cluster-triage skill (symptoms → playbooks) and a manifest-review skill. Facts about *your* machines in `docs/` beat those skills' generic advice (a vSphere / Tanzu cluster is not EKS; a bare-metal HAProxy is not an ALB). ## 1. Getting on a machine ```bash S=skills/devops/change/scripts $S/jssh.py 'hostname' # the jump host $S/jssh.py --host 10.0.0.48 'docker ps' # another VM, via -J $S/jssh.py --sudo --host 10.0.0.48 'ss -tlnp' $S/jssh.py --kube 'kubectl get pods -A' # runs the [kube] token refresh first $S/jssh.py --forward 15211:10.0.0.53:1521 # DB tunnel through the jump host $S/snapshot_haproxy.sh 10.0.0.48 snapshots # what every HAProxy container is really running ``` Credentials come from `~/.config/devops/hosts.ini` (`[ssh]` / `[kube]`, layout in the script's docstring; `chmod 600`, never inside a repo). **Never put a password on a command line, in a report or in chat.** `Connection timed out during banner exchange` = your VPN is down; tell the user, do not loop on retries. ## 2. Severity — decide before acting, write it at the top of the report | level | means