helm-framework-migration
/helm-framework-migration
Migrate an existing hand-rolled Helm chart onto the helm-framework library chart, check the migration for regressions, and clean up orphaned values.yaml keys. Use when moving a chart from bespoke templates to helm-framework, auditing a migration that already landed, or investigating whether a values.yaml key still does anything after such a migration.
- Author
- k8s-stuff ↗
- Repository
- helm-framework ↗
- Licence
- MIT
- Last repository change
- 29.09.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 29.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Migrate an existing hand-rolled Helm chart onto the helm-framework library chart, check the migration for regressions, and clean up orphaned values.yaml keys. Use when moving a chart from bespoke templates to helm-framework, auditing a migration that already landed, or investigating whether a values.yaml key still does anything after such a migration.
Original author description
Migrate an existing hand-rolled Helm chart onto the helm-framework library chart, check the migration for regressions, and clean up orphaned values.yaml keys. Use when moving a chart from bespoke templates to helm-framework, auditing a migration that already landed, or investigating whether a values.yaml key still does anything after such a migration.
How it works
- What this skill does
- The five phases
SKILL.md preview
--- name: "helm-framework-migration" description: "Migrate an existing hand-rolled Helm chart onto the helm-framework library chart, check the migration for regressions, and clean up orphaned values.yaml keys. Use when moving a chart from bespoke templates to helm-framework, auditing a migration that already landed, or investigating whether a values.yaml key still does anything after such a migration." --- # helm-framework migration ## What this skill does Guides migrating an existing chart's hand-rolled templates onto `helm-framework` (v1.6.0 at generation time) safely. This is a distinct, harder job from scaffolding a new chart (see the `helm-framework` skill for that): `helm-framework` reads the consumer's flat `.Values` directly, with no `additionalProperties: false` enforcement, so a value nothing reads after migration is silently ignored — the chart still renders, still deploys, and gives no error. This skill exists to catch that failure mode before it ships. Works both as a forward-driven migration (you are about to migrate a chart) and as a post-hoc audit (a migration already landed and you want to check it). ## The five phases 0. **Preflight** — check the consumer's dependency pin, this skill's own baked version, and the newest published version all agree. Advisory only; never blocks. 1. **Baseline capture** — render the chart before migrating (or, in audit mode, at the commit before the migration) and record the exact `helm template` invocation for later replay. 2. **Migration** — add the dependency, replace hand-rolled templates with the library's `include`, and map old value keys onto library keys using the `helm-framework` skill's `resources/values-reference.md`. Skipped in audit mode. 3. **Regression check** — replay the recorded invocation post-migration and diff a fixed critical-field checklist, resource-by-resource, matched by kind and role rather than by name. 4. **Orphan classification and cleanup** — find `values.yaml` keys nothing reads anymore, tier them by confidence, and auto-remove only the tier with a render-equality proof. Full detail for every phase — the exact checklist, the cosmetic-churn ignore list, the orphan tiers, and the resemblance rule used to catch near-miss renames — is in `resources/migration-playbook.md`. `resources/values-contract.md` is the generated, authoritative answer to "does the library read this key?" — phase 4 depends on it.
Files in this package (3)
- SKILL.md 2 KB
- resources/migration-playbook.md 12 KB
- resources/values-contract.md 9 KB
Versions
The database has no other skills named helm-framework-migration.
Database snapshot: 13.11.2026 · package version e20c503c2b01 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100helm-framework
Scaffold and configure Helm charts that depend on the helm-framework library chart. Use when adding helm-framework as a Helm dependency, writing values.yaml for a chart built on it, or looking up what a value controls. - 90helm-chart-quality-review
Use this skill when a user provides a Helm chart or asks to review Helm chart quality, security, or testability — including Chart.yaml, values.yaml, templates/, tests/, or chart-testing CI configuration. - 100k8s
Kubernetes and Helm review and scaffolding for EKS workloads. Use when user says 'review my helm values', 'before I deploy', 'scaffold a new service', 'check values.yaml', or when working in values.yaml, Chart.yaml, or Helm template files. - 85kubernetes-helm-review
Use when reviewing Helm chart structure, values, templates, and best practices. Only triggers when Chart.yaml is detected. - 100generating-helm-charts
Execute use when generating Helm charts for Kubernetes applications. Trigger with phrases like "create Helm chart", "generate chart for app", "package Kubernetes deployment", or "helm template". Produces production-ready charts with Chart.yaml, values.yaml, templates, and best… - 100generating-helm-charts
Execute use when generating Helm charts for Kubernetes applications. Trigger with phrases like "create Helm chart", "generate chart for app", "package Kubernetes deployment", or "helm template". Produces production-ready charts with Chart.yaml, values.yaml, templates, and best…