.claude/skills/helm-deploy/SKILL.md
Safe Helm deployment with image verification, cache busting, and rollback safety. Prevents deploying stale images.
npx skillsauth add markus41/claude helm-deployInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Deploy via Helm with image verification: $ARGUMENTS
Verify the image exists in the registry
# ACR
az acr repository show-tags --name <registry> --repository <image> --orderby time_desc --top 5
# Docker Hub
docker manifest inspect <registry>/<image>:<tag>
Check what's currently running
helm list -n <namespace>
kubectl get pods -n <namespace> -o jsonpath='{range .items[*]}{.metadata.name}{"\t"}{range .spec.containers[*]}{.image}{"\n"}{end}{end}'
Diff the changes before applying
helm diff upgrade <release> <chart> -n <namespace> \
--set image.tag=<new-tag> \
--set image.pullPolicy=Always \
-f values.yaml
helm upgrade --install <release> <chart> \
--namespace <namespace> \
--set image.repository=<registry>/<image> \
--set image.tag=<specific-tag> \
--set image.pullPolicy=Always \
--atomic \
--wait \
--timeout 5m \
-f values.yaml
# Verify new pods are running
kubectl rollout status deployment/<deployment> -n <namespace>
# Verify the correct image is running
kubectl get pods -n <namespace> -o jsonpath='{range .items[*]}{.metadata.name}{"\t"}{range .spec.containers[*]}{.image}{"\n"}{end}{end}'
# Check pod logs for startup errors
kubectl logs -l app=<app> -n <namespace> --tail=50
helm rollback <release> -n <namespace>
# Or to a specific revision:
helm history <release> -n <namespace>
helm rollback <release> <revision> -n <namespace>
--set image.tag=<specific> with a unique tag (git SHA, semver)--set image.pullPolicy=Always to force fresh pulls--atomic for automatic rollback on failure--wait to confirm pods are healthy:latest as the only tagdevelopment
Enhanced plan-authoring skill with Pre-Writing context gathering, task metadata, non-TDD templates, Red Flags, telemetry, and an automated plan linter. Use when you have a spec or requirements for a multi-step task, before touching code.
tools
Documentation intelligence engine with graph-based API docs, algorithm library, and drift detection
tools
Ultraplan cloud planning — kick off a plan in the cloud from your terminal, review and revise in the browser, then execute remotely or send back to CLI
tools
--- name: mcp description: Configure MCP servers for Claude Code — stdio vs HTTP, authentication, Tools/Resources/Prompts distinction, channels (CI webhook, mobile relay, Discord bridge, fakechat), and cost of always-loaded tools. Use this skill whenever adding an MCP server, debugging connection issues, choosing between MCP Tools vs Prompts vs Resources, installing channel servers, or managing .mcp.json. Triggers on: "MCP server", "mcp config", "add Obsidian MCP", "install context7", "channels"