helm-update

Applies Bifrost Helm chart updates and syncs values with config.schema.json changes.

7.7k|1.1k|Updated Mar 19, 2025
One-click install
npx skills add https://github.com/maximhq/bifrost --skill helm-update
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: helm-update
Source: https://github.com/maximhq/bifrost/tree/main/.claude/skills/helm-update
Command: npx skills add https://github.com/maximhq/bifrost --skill helm-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeping the Bifrost Helm chart in sync with the evolving config.schema.json is error-prone: new config fields get added to the gateway but never surface in values.yaml, values.schema.json, or the _helpers.tpl template, and changelogs fall behind. This Skill automates the entire update cycle so no field is silently dropped.

Core Features & Use Cases

  • Schema Gap Detection: Diffs transports/config.schema.json against the last helm release commit to find fields not yet reflected in the chart, then closes those gaps automatically.
  • Coordinated Chart Updates: Updates values.yaml (commented samples), values.schema.json (typed properties), _helpers.tpl (config.json rendering), and bumps the Chart.yaml version in one pass.
  • Changelog Automation: Updates the helm README Latest Version and Upcoming sections, creates a docs/changelogs/helm-v<version>.mdx file, and registers it in docs.json navigation.
  • Use Case: After merging a PR that adds a new load-balancer option to config.schema.json, invoke the skill to propagate that option through the Helm chart, bump the version, and generate all changelog entries, ending with a diff review verifying every new field maps back to the schema.

Quick Start

Invoke /helm-update and describe the Helm chart changes you want applied, such as adding a new config field or syncing recent schema changes.

Frequently Asked Questions about helm-update

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

FAQPage Schema
How do I update a Helm chart when the application config schema changes?▼

Diff config.schema.json against the last helm release commit to find new or changed fields, then add them to values.yaml as commented samples, values.schema.json as typed properties, and _helpers.tpl so they render into the generated config.json.

How do I add a new field to values.yaml and values.schema.json?▼

Add the field to values.yaml as a commented-out block with a realistic sample value near related fields, then add a matching property in values.schema.json with the correct type, description, and any enum, default, or range constraints.

How do I render Helm values into a config.json with _helpers.tpl?▼

Wrap optional fields in {{- if .Values... }} guards inside the bifrost.config define block and pipe values through toJson, for example "read_buffer_size": {{ .Values.bifrost.server.readBufferSize | toJson }}.

Does this skill decide the Helm chart version bump automatically?▼

It increments the patch version in Chart.yaml by default and asks the user when the scope of changes might warrant a minor bump instead.

What happens if a config.schema.json field has no Helm mapping?▼

The final diff review checks every new field against config.schema.json. If a mapping is missing or too complex, such as a new top-level plugin system, the skill flags it to the user rather than silently skipping it.