devops-changelisted
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