publish-helm

Publishes Helm charts to OCI registries through prep, tagging, and pull verification.

7|5|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/nebius/nebius-ps-services --skill publish-helm-nebius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish-helm
Source: https://github.com/nebius/nebius-ps-services/tree/main/skills/publish-helm
Command: npx skills add https://github.com/nebius/nebius-ps-services --skill publish-helm-nebius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve? Publishing a Helm chart release involves many error-prone manual steps: bumping Chart.yaml versions, updating changelogs, creating release branches and PRs, tagging from the correct branch, waiting for CI, and verifying the published OCI artifact. This Skill automates that entire release workflow with strict guardrails. ## Core Features & Use Cases - End-to-End Release Execution: Runs setup, prep, publish, or complete modes covering changelog updates, Chart.yaml version bumps, strict lint and template validation, release branch creation, PR merge, and annotated tag push. - OCI Verification: Confirms the published chart by pulling it from the OCI repository base with helm pull after the tag-triggered workflow completes. - Safety Guardrails: Requires a clean synced default branch, explicit release tags (never inferred), and stops on missing approvals, failing checks, or dirty worktrees. - Use Case: A platform engineer asks to publish chart version 1.4.0; the Skill preps the release branch, merges the PR, tags the release, waits for the GitHub Actions workflow, and verifies the OCI chart pull. ## Quick Start Ask the agent to publish the Helm chart in the current project with publish-helm in complete mode using tag 1.4.0 and your OCI repository base.

Frequently Asked Questions about publish-helm

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

FAQPage Schema
How do I publish a Helm chart to an OCI registry?

Run the skill in complete mode with an explicit tag and OCI repository base. It preps a release branch with the Chart.yaml version bump, merges the PR, pushes the annotated tag, waits for the publish workflow, and verifies with helm pull.

How to automate Helm chart releases with GitHub Actions?

The skill pushes an annotated tag from the clean synced default branch, which triggers the project's tag-based chart publish workflow. It then watches the run with gh run watch and verifies the resulting OCI chart.

Can I publish a Helm chart from a feature branch?

No. Prep and publish must run from the clean, synced default branch. If you are on a feature branch or have uncommitted changes, the skill stops and asks you to merge to the default branch first.

Why does Helm chart publishing fail with a version mismatch?

The publish phase fails fast when Chart.yaml does not match the release tag version. Run prep mode first to bump the chart version and changelog, merge that PR, then publish the tag.

What should the OCI repository value include for helm push?

Pass only the OCI repository base such as oci://registry.example.com/org/charts, without the chart name or version. Helm derives the chart reference from Chart.yaml metadata, and verification appends the chart name and version.