bifrost:release

Automate Bifrost's three-rung release workflow with pre-release checks and Kubernetes deployment.

55|14|Updated Oct 12, 2025
One-click install
npx skills add https://github.com/gobifrost/bifrost --skill bifrost-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bifrost:release
Source: https://github.com/gobifrost/bifrost/tree/main/.claude/skills/bifrost-release
Command: npx skills add https://github.com/gobifrost/bifrost --skill bifrost-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Bifrost's release process spans three distinct rungs (dev, pre-release, full release) with mandatory pre-checks, plugin manifest synchronization, contributor attribution, release notes drafting, and Kubernetes deployment steps, all of which are complex and error-prone to manage manually.

Core Features & Use Cases

  • Three-rung release orchestration: Handles dev pushes (CI :dev image builds on main merge), pre-release candidate tagging (vX.Y.Z-rc.N tags with pre-release GitHub Releases), and full stable releases (vX.Y.Z tags with :latest images and final GitHub Releases).
  • Automated pre-release guardrails: Runs unit tests, documentation freshness checks, plugin manifest version guards, external contributor attribution cross-checks, and CVE tracking to ensure releases meet OpenSSF Best Practices criteria.
  • Use Case: A Bifrost maintainer merging a new feature to main can use this skill to automatically validate tests, push the dev image, and get clear instructions for K8s rollout, or cut a full production release with properly attributed release notes without missing any mandatory steps.

Quick Start

Invoke the bifrost-release skill to handle the full end-to-end stable release process for Bifrost after merging all changes to the main branch, including pre-release checks, release notes drafting, and version tag pushing.

Frequently Asked Questions about bifrost:release

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

FAQPage Schema
How do I automate Kubernetes deployment rollouts after cutting a GitHub release?

Automating Kubernetes deployment rollouts after a GitHub release requires orchestrating container image tagging with stable version tags. This skill triggers K8s rollouts by syncing plugin manifests and pushing :latest images following pre-release candidate validation.

What are the mandatory pre-release checks for meeting OpenSSF Best Practices criteria?

Mandatory pre-release checks for OpenSSF Best Practices include unit test validation, documentation freshness verification, CVE tracking, and SemVer tag compliance. This skill automates these guardrails alongside external contributor attribution cross-checks before drafting release notes.

How do I manage pre-release candidate tagging and dev CI pushes for container images?

Managing pre-release candidate tagging involves applying vX.Y.Z-rc.N tags with pre-release GitHub Releases, while dev CI pushes build :dev images on main branch merges. This skill automates this three-rung workflow spanning dev, pre-release, and full stable releases.

Can I synchronize plugin manifest versions and external contributor attribution during release automation?

Synchronizing plugin manifest versions and attributing external contributors are core features of this release automation skill. It cross-checks contributor attribution and enforces manifest version guards automatically before pushing final stable version tags and drafting release notes.

What is the best way to handle multi-stage release orchestration from dev pushes to production?

Handling multi-stage release orchestration requires automating dev CI image builds, pre-release candidate tagging, and full stable version releases. This skill coordinates the entire workflow, enforcing pre-release guardrails and managing Kubernetes deployment rollouts end-to-end.