Automate the full application release flow for BrewMate, including committing local changes, bumping version, waiting for GitHub Actions release build, and pushing the in-repo cask update…
Install the "release-flow" agent skill from https://github.com/romankurnovskii/BrewMate/tree/main/.agents/skills/release-flow into .claude/skills/release-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-flow", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add romankurnovskii/BrewMate --skill release-flow -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "release-flow" agent skill from https://github.com/romankurnovskii/BrewMate/tree/main/.agents/skills/release-flow into .agents/skills/release-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-flow", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add romankurnovskii/BrewMate --skill release-flow -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "release-flow" agent skill from https://github.com/romankurnovskii/BrewMate/tree/main/.agents/skills/release-flow into .cursor/skills/release-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-flow", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add romankurnovskii/BrewMate --skill release-flow -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "release-flow" agent skill from https://github.com/romankurnovskii/BrewMate/tree/main/.agents/skills/release-flow into .gemini/skills/release-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-flow", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add romankurnovskii/BrewMate --skill release-flow -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "release-flow" agent skill from https://github.com/romankurnovskii/BrewMate/tree/main/.agents/skills/release-flow into .github/skills/release-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-flow", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add romankurnovskii/BrewMate --skill release-flow -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "release-flow" agent skill from https://github.com/romankurnovskii/BrewMate/tree/main/.agents/skills/release-flow into .opencode/skills/release-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-flow", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
release-flow
GitHub stars
301
Token cost
~976 tokens
SKILL.md length
455 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
MIT
At a glance
Automate the full application release flow for BrewMate, including committing local changes, bumping version, waiting for GitHub Actions release build, and pushing the in-repo cask update…
Works in 5 steps: Pre-Release Verification → Stage and Commit Outstanding Changes → Bump Version and Push Tag → …
This skill whenever the user mentions releasing a new version
SKILL.md covers Prerequisites, Step-by-Step Instructions and Success Criteria
Calls npm and git; needs GITHUB_TOKEN
What it does
Release Flow is an agent skill from romankurnovskii/BrewMate. Automate the full application release flow for BrewMate, including committing local changes, bumping version, waiting for GitHub Actions release build, and pushing the in-repo cask update (Casks/brewmate.rb). Trigger this skill whenever the user mentions releasing a new version, deploying the application, publishing version, or running the cask release workflow.
Its SKILL.md is about 980 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering CI/CD and App store release. It works with GitHub Actions, Homebrew, GitHub and React. The repository describes itself as: Homebrew GUI apps manager. The licence is MIT.
When your agent uses it
This skill whenever the user mentions releasing a new version
Deploying the application
Publishing version
Running the cask release workflow
Example prompts
“/release-flow”
Requirements
A credential in GITHUB_TOKEN
Workflow steps
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit c581aff. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npm
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
GITHUB_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Release Flow loads about 976 tokens when it runs. Until then it costs about 94 tokens; SKILL.md has 455 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~94
When it runs· the whole SKILL.md, loaded when a task matches
~976
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Download SKILL.mdSave it as .claude/skills/release-flow/SKILL.md (or your agent's skills folder).
name
release-flow
description
Automate the full application release flow for BrewMate, including committing local changes, bumping version, waiting for GitHub Actions release build, and pushing the in-repo cask update (Casks/brewmate.rb). Trigger this skill whenever the user mentions releasing a new version, deploying the application, publishing version, or running the cask release workflow.
Release Flow Skill
This skill automates the end-to-end application release cycle for BrewMate. It guides the model through running local verifications, committing changes, bumping the version, pushing tags, tracking the release workflow run on GitHub, and merging the corresponding Cask update PR in the custom Homebrew tap.
Prerequisites
Ensure the local workspace is clean (git status).
Ensure the GitHub CLI (gh) is authenticated on the user system.
Since the agent environment may contain a dummy GITHUB_TOKEN that overrides your keyring, prefix GitHub CLI commands with env -u GITHUB_TOKEN to use the active keyring credentials.
Step-by-Step Instructions
1. Pre-Release Verification
Before making any release, ensure the codebase compiles and passes all checks.
Run unit tests:bash
npm test
Run the build script to compile the TypeScript files:bash
npm run build
If any checks fail, stop and report the errors to the user. Do not proceed with the release until the code is fully verified.
2. Stage and Commit Outstanding Changes
Stage all modified files and commit them using Conventional Commits.
Stage all local changes:bash
git add .
Identify the staged files to ensure only the expected files are staged:bash
git diff --cached --name-only
Commit using Conventional Commits:bash
git commit -m "fix: resolve stuck loading state for categories donut chart"
(Modify the commit type and message dynamically based on the changes you are releasing).
3. Bump Version and Push Tag
Bump the package version and push the changes together with the tag to trigger the GitHub Actions release workflow.
Bump the version (defaults to a patch release, e.g., npm version patch):bash
npm version patch
(If the user explicitly requests a minor or major release, run npm version minor or npm version major instead).
Push the commit and its corresponding tag to the remote repository:bash
git push origin main --follow-tags
Show full SKILL.md (200 more words)Show less
4. Monitor GitHub Actions Release Run
Query the workflow runs to track the progress of the release build.
List the most recent workflow runs:bash
env -u GITHUB_TOKEN gh run list --limit 5
Identify the run corresponding to the new version tag (e.g. 1.0.26 under the Release workflow).
If the run is queued or in_progress, wait and check periodically (e.g., using a background scheduler or timer) until the status changes to completed and the conclusion is success.
If the build fails, notify the user immediately.
5. Cask Updated In-Repo (No External PR Needed)
Once the GitHub Actions Release build completes successfully, the create-release.yml workflow automatically:
Updates Casks/brewmate.rb in this repo with the new version and SHA256.
Commits and pushes the change directly to main with [skip ci].
No external PR to romankurnovskii/homebrew-awesome-brew is needed. The cask is now maintained in-repo — the release workflow pushes the updated cask directly to the BrewMate repository's main branch.
To verify the cask update:
bash
git pull origin main
cat Casks/brewmate.rb
Success Criteria
The release flow is complete when:
The new version tag is pushed.
The GitHub Actions release build completes successfully.
The Casks/brewmate.rb file is updated with the new version and SHA256 on the main branch.
Release Flow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
A skill your agent uses when adding or editing a GitHub Actions workflow that pushes a container image to a registry (ECR/ghcr/Docker Hub via build-push-action) or dispatches a production deploy (a…
A skill your agent uses when editing, adding, or reviewing any file under .github/workflows/, or when a CI step installs a CLI tool (npm i -g, npx, pipx, uses: /setup-).
A skill your agent uses whenever the user asks for a new npm version, npm release, package release, new release, version bump, publishing to npm, cutting a GitHub release, tagging a release, or…
Automate the full application release flow for BrewMate, including committing local changes, bumping version, waiting for GitHub Actions release build, and pushing the in-repo cask update…. Release Flow is an agent skill from romankurnovskii/BrewMate.rb).
When should I use Release Flow?
Release Flow fits situations like: this skill whenever the user mentions releasing a new version; deploying the application; publishing version; running the cask release workflow.
How do I install Release Flow in Claude Code?
Run `npx skills add romankurnovskii/BrewMate --skill release-flow -a claude-code`. Or copy the skill folder (.agents/skills/release-flow in romankurnovskii/BrewMate) into .claude/skills/release-flow in your project. Claude Code loads it when a task matches its description.
How do I install Release Flow in Codex?
Run `npx skills add romankurnovskii/BrewMate --skill release-flow -a codex`. Or copy the skill folder (.agents/skills/release-flow in romankurnovskii/BrewMate) into .agents/skills/release-flow in your project. Codex loads it when a task matches its description.
Can I use Release Flow in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add romankurnovskii/BrewMate --skill release-flow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-flow, .gemini/skills/release-flow, .github/skills/release-flow and .opencode/skills/release-flow in your project.
What does Release Flow need to run?
Going by SKILL.md and its folder, Release Flow needs the command-line tools its instructions call (npm and git) and credentials named GITHUB_TOKEN. Our summary lists: A credential in GITHUB_TOKEN.
Does Release Flow access the network?
SKILL.md contains no URLs. Its commands use npm and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Release Flow safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Release Flow use?
Release Flow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Release Flow use?
About 976 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Release Flow?
Skills that share tags, products or a category with Release Flow: Gating Production Deploys (PostHog/posthog, 40k stars), GitHub Actions Supply Chain Pinning (asyncapi/generator, 1.1k stars), npm Release Via GitHub Actions (jmfederico/pi-web, 869 stars) and Release (jtenniswood/espframe, 209 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release Flow?
romankurnovskii (a GitHub user) maintains it in romankurnovskii/BrewMate, which has 301 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 28, 2026.
Source: romankurnovskii/BrewMate on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
