skills.rest
benkruger
benkrugerCOMMUNITY
Explore all skills by this author →
GitHub

flow-release

Automate FLOW plugin releases by bumping versions and publishing GitHub releases.

25|3|Updated Feb 19, 2026
Search Tags:#git#workflow#plugin#release#flow#notes#ci
One-click install
npx skills add https://github.com/benkruger/flow --skill flow-release
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flow-release
Source: https://github.com/benkruger/flow/tree/main/.claude/skills/flow-release
Command: npx skills add https://github.com/benkruger/flow --skill flow-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Releasing the FLOW plugin is a repetitive, error-prone process. This skill provides a repeatable, auditable workflow that bumps versions, updates plugin and marketplace metadata, and publishes a GitHub release.

Core Features & Use Cases

  • Version bumping: automatically increments plugin and marketplace versions across files.
  • Release publishing: creates a GitHub release and synchronizes marketplace entry.
  • Workflow governance: includes pre-flight checks, CI verification, and safe tagging to prevent regressions.

Quick Start

Run the release workflow to bump the version, commit changes, tag, and publish the GitHub release.

Frequently Asked Questions about flow-release

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

FAQPage Schema
How do I automate a GitHub release workflow for a plugin?▼

Automating a GitHub release workflow involves bumping versions, updating metadata files like plugin.json and marketplace.json, and publishing the release. This process enforces pre-flight checks and CI verification to ensure safe, auditable releases.

What is the best way to bump plugin versions across multiple files before tagging?▼

Bumping plugin versions requires automatically incrementing the version numbers across both plugin.json and marketplace.json files. This ensures metadata synchronization before committing changes, tagging, and publishing the release.

Do I need push access and CI checks to run an automated release workflow?▼

Yes, automated release workflows target maintainers with push access and require passing CI checks on a proper branch. These pre-flight checks prevent regressions and ensure safe, auditable releases.

How does marketplace synchronization work during a plugin release?▼

Marketplace synchronization updates the marketplace.json file with the new version metadata during the release workflow. This happens automatically before creating a GitHub release, ensuring the marketplace entry stays current.

What pre-flight checks are needed before creating a GitHub release tag?▼

Pre-flight checks for GitHub release tagging verify CI status, proper branching, and push access permissions. These governance steps prevent regressions and ensure safe, auditable releases before version bumping and publishing.

Can I draft release notes automatically when publishing a GitHub plugin release?▼

Yes, the release workflow drafts release notes as part of the automated process. It bumps versions, updates plugin and marketplace metadata, drafts notes, and creates the GitHub release end-to-end.

Related Skills

Explore More Software Engineering Skills→
darylmcddarylmcd

bump

Bump project versions across five files and consolidate changelog fragments.

Community
Intermediate
sscciossccio

release

Automates oh-my-claudecode release workflow with npm publish and GitHub tagging.

Community
Intermediate
ImBIOSImBIOS
1

release

Automate version bumps and npm releases for the swarm-tools monorepo.

Community
Advanced
global-osglobal-os

release

Automate vercel-plugin releases with pre-flight checks, version bumps, and git operations.

Official
Advanced