feat(k9s): automatic danger skin for production clusters

[Copilot]

k9s gives no visual indication when you're operating on a production cluster, making it easy to accidentally apply destructive changes.

Changes

• .aliases — adds a k9s bash function that inspects the active kubectl context at launch time; if the context name contains prd (case-insensitive), it sets K9S_SKIN=prd for that invocation before calling the real binary via command k9s.

• .config/k9s/skins/prd.yml — red-tinted danger skin derived from the existing Dracula theme. Uses a dark red background (#1c0000), red borders, logo, and accent colours to make the production context immediately unmistakable.

• .gitignore — adds !.config/k9s/skins/ exception, consistent with the existing !.config/k9s/skin.yml rule, so the new skins directory is tracked.

# Non-prd context → normal Dracula skin
$ kubectl config use-context staging-eu && k9s

# Any context containing "prd" → danger red skin applied automatically
$ kubectl config use-context prod-eu-prd && k9s  # K9S_SKIN=prd

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

[bdossantos]

@copilot is possible to achieve this via an alias or bash function ?

[Copilot]

@copilot is possible to achieve this via an alias or bash function ?

Done in 577c8e0. Replaced bin/k9s with a k9s bash function in .aliases:

if command -v k9s &>/dev/null; then
  function k9s() {
    local context
    context="$(kubectl config current-context 2>/dev/null || true)"
    if [[ -n "$context" && "${context,,}" == *prd* ]]; then
      K9S_SKIN="${K9S_SKIN:-prd}" command k9s "$@"
    else
      command k9s "$@"
    fi
  }
fi

command k9s bypasses the function to call the real binary. The ${context,,} lowercase expansion ensures contexts like PRD or Prd are caught too.