Find out why it works in staging but not production
Compares configurations across your environments — Terraform state, Helm values, env vars, K8s resources — and surfaces every difference. The fastest way to find the manual change someone made in production 6 months ago.
Create a skill called "Env Diff". Compare configurations across environments to find drift: 1. Compare Terraform variables (tfvars) across workspaces 2. Diff Helm values.yaml files across environments 3. Compare K8s resources using `kubectl diff` or by fetching and comparing manifests 4. Diff environment variables from deployment configs 5. Identify resources that exist in one environment but not another For each difference found: - Classify as: intentional (different sizing), drift (manual change), or missing (exists in one env only) - Flag security-relevant differences (IAM, security groups, encryption, network policies) - Suggest whether to align or document the difference Present as a clean diff report, organized by severity.
Environment drift causes outages that are uniquely frustrating because the
code is the same — it's the configuration that differs. This skill diffs
your environments systematically.
Diagnose CrashLoopBackOff and friends without the kubectl marathon
Give it a namespace or pod name and it runs the full kubectl diagnostic sequence for you — events, logs, describe, resource usage — then explains what's actually wrong in plain English. No more chaining five commands to find out you're missing an environment variable.
Find out who made that "quick fix" in the AWS console
Runs Terraform drift checks across your workspaces and surfaces everything that's drifted from your declared state. Catches manual console changes, forgot-to-import resources, and environment inconsistencies before they cause the next outage.
A playbook for "stops at the same frame" and "freeze mid-render" failures
Renders freeze at a consistent percentage or frame — often caused by a bad clip, a heavy effect, a Fusion comp issue, or "stop render on error" settings. This recipe classifies the failure pattern and gives you a structured triage plan instead of blind re-exports.
Fix a common Premiere playback-lag issue caused by audio input device settings
Severe playback lag and stutter in Premiere Pro that looks like a codec performance problem but is actually caused by audio hardware input settings. This recipe provides a quick decision tree to test and fix the issue — often resolved in under a minute by switching the default input to "No Input."