release

Automate Cloudflare-Operator release workflows with version bumps, changelogs, Git tags, and GitHub releases.

6|4|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/StringKe/cloudflare-operator --skill release-stringke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/StringKe/cloudflare-operator/tree/main/.claude/skills/release
Command: npx skills add https://github.com/StringKe/cloudflare-operator --skill release-stringke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

cloudflare-operator 的版本发布流程通常涉及版本号维护、变更日志、Git 标签以及 GitHub Release 的协同工作。本技能提供一个清晰、可重复的工作流来简化并标准化发布过程。

Core Features & Use Cases

  • 版本号更新与标签创建的自动化管理
  • 变更日志模板化生成与发布流程编排
  • GitHub Release 资产打包与发布流水线集成
  • 适用于新的版本发布、分支发布与回滚场景

Quick Start

在仓库根目录执行发布流程,系统将引导你完成版本号确认、标签创建与 GitHub Release 的发布。

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate GitHub releases and Git tagging for the Cloudflare-Operator?

Automate GitHub releases and Git tagging for the Cloudflare-Operator by executing the release workflow in your repository root, which handles version bumping, tag creation, and GitHub Release publishing in CI contexts.

What is the best way to update changelogs and version numbers across release branches?

Updating changelogs and version numbers across branches is handled by templated changelog generation and automated version bump management. This coordinates release notes and version formatting consistently across new releases and branch rollbacks.

Can I use this release workflow for branch releases and rollback scenarios?

Yes, you can use this release workflow for branch releases and rollback scenarios. It coordinates changelogs across branches and handles version formatting, tag creation, and artifact publishing to manage these specific release engineering tasks effectively.

How does the release process package and publish GitHub Release assets?

The release process packages and publishes GitHub Release assets by integrating asset packaging into the publishing pipeline. It automates the preparation of new versions and coordinates the release notes alongside the published artifacts in CI contexts.

Do I need a CI environment to manage Git tags and version bumps?

A CI environment is not strictly required to manage Git tags and version bumps, as you can execute the workflow from the repository root. However, the workflow is designed to meet requirements for artifact publishing and release notes in CI contexts.