helm-expert

Provides Helm 3 reference guidance for chart authoring, values merging, hooks, and release workflows.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/psmfd/pi-config --skill helm-expert-psmfd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: helm-expert
Source: https://github.com/psmfd/pi-config/tree/main/agent/skills/helm-expert
Command: npx skills add https://github.com/psmfd/pi-config --skill helm-expert-psmfd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Helm deployments frequently fail due to misunderstood values merge semantics, misconfigured hooks, and untested template changes. This Skill gives an AI agent a structured Helm 3 reference so it can answer questions and review charts accurately without guessing. ## Core Features & Use Cases - Values Merge Semantics: Explains the maps-merge/lists-replace rule, precedence ordering of -f files versus --set, and subchart values scoping including global.*. - Hooks and Releases: Documents hook types, weights, deletion policies, the hook-failed accumulation trap, and release workflows like --atomic, --wait, and rollback limitations. - Template Debugging and Diff Validation: Covers helm template, --dry-run modes, the lookup empty-cluster trap, whitespace control, and helm diff comparison semantics against the last successful release. - Use Case: When a helm upgrade fails because a list in values was unexpectedly replaced, the agent can diagnose the merge behavior and recommend the correct layering of values files. ## Quick Start Ask the agent to explain why your Helm values list was overwritten during an upgrade and how to structure values files for multiple environments.

Frequently Asked Questions about helm-expert

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do Helm values merge when using multiple -f files?▼

Helm deep-merges maps but completely replaces lists, which is the most common deployment surprise. `-f` files apply left to right with later files winning, and `--set` always overrides any `-f` file.

How do I preview Helm template changes before upgrading?▼

Use `helm template` for local rendering or `helm diff upgrade` to compare against the last successful release. Note that `helm diff` ignores manual `kubectl edit` changes, which the upgrade will overwrite.

Why does my Helm upgrade fail after a hook failed previously?▼

A failed hook without a deletion policy leaves its resource in the cluster, so the next upgrade fails because the resource already exists. Set `helm.sh/hook-delete-policy: before-hook-creation` to avoid accumulation.

Does helm rollback undo database migrations or hook side effects?▼

No. `helm rollback` only reverts manifests and values to a previous revision. Database migrations, external config changes, and hook side effects are not reverted and must be handled separately.

Why does my Helm template using lookup render empty values?▼

The `lookup` function returns an empty dict during `helm template` and `--dry-run=client` because there is no cluster connection. Templates using `lookup` must handle the empty case gracefully.