How do I install the Gf Release skill?

Run npx skillmds@latest add codejunkie99/gf-release in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gf Release safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gf Release?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gf Release free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gf Release?

codejunkie99 (@codejunkie99) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gf Release by codejunkie99 — Agent Skill

Name: Gf Release
Author: codejunkie99

Gf Release

GateFlow release readiness workflow. Validates plugin manifests, marketplace metadata, docs index coverage, root mirrors, release notes, and component counts before a version tag is created. Use when preparing, checking, or cutting a GateFlow plugin release.

codejunkie99 06dccd9 2.5 KB Updated Sep 17, 2026

File contents

allowed-tools:

Bash
Read
Edit
Write
Glob
Grep

GF-Release -- Release Readiness

Use this workflow before tagging or publishing GateFlow.

Required Inputs

Target version, for example 2.5.0
Whether this is check-only or a release-prep edit

If no version is provided, inspect plugins/gateflow/.claude-plugin/plugin.json and propose the next semver version based on the changes:

Change Type	Version Bump
Metadata, docs, or packaging fix	Patch
New command, skill, agent, IP, or board	Minor
Breaking plugin layout or workflow change	Major

Release Checks

Run the deterministic validator from the repo root:

python3 tools/validate_gateflow.py --version <target-version>

The validator must pass before creating a tag. It checks:

plugin and marketplace JSON version consistency
component counts in descriptions and READMEs
docs/gateflow.index coverage for every command, skill, and agent
root-level mirrors for every command-adjacent skill and agent file
a release note entry for the target version

Prep Workflow

Count actual components:

find plugins/gateflow/agents -maxdepth 1 -name '*.md' | wc -l
find plugins/gateflow/skills -maxdepth 2 -name 'SKILL.md' | wc -l
find plugins/gateflow/commands -maxdepth 1 -name '*.md' | wc -l

Update version strings:

plugins/gateflow/.claude-plugin/plugin.json
.claude-plugin/marketplace.json

Update release-facing docs:

README.md
plugins/gateflow/README.md
docs/gateflow.index
releases.md

Run validator and focused tests:

python3 -m unittest tests/test_validate_gateflow.py
python3 tools/validate_gateflow.py --version <target-version>

Only after validation passes, tag and release:

git tag v<target-version>
gh release create v<target-version> --title "GateFlow v<target-version>" --notes-file <notes-file>

Report Format

---GATEFLOW-RESULT---
STATUS: PASS | FAIL
VERSION: <target-version>
INVENTORY: <agents> agents, <skills> skills, <commands> commands, <ip> IP, <boards> boards
FILES: <changed release-facing files>
DETAILS: <summary or validation failures>
---END-GATEFLOW-RESULT---

---name: gf-releasedescription: GateFlow release readiness workflow. Validates plugin manifests, marketplace metadata, docs index coverage, root mirrors, release notes, and component counts before a version tag is created. Use when preparing, checking, or cutting a GateFlow plugin release.---allowed-tools: - Bash - Read - Edit - Write - Glob - Grep# GF-Release -- Release ReadinessUse this workflow before tagging or publishing GateFlow.## Required Inputs- Target version, for example `2.5.0`- Whether this is check-only or a release-prep editIf no version is provided, inspect `plugins/gateflow/.claude-plugin/plugin.json`and propose the next semver version based on the changes:| Change Type | Version Bump ||---|---|| Metadata, docs, or packaging fix | Patch || New command, skill, agent, IP, or board | Minor || Breaking plugin layout or workflow change | Major |## Release ChecksRun the deterministic validator from the repo root:```bashpython3 tools/validate_gateflow.py --version <target-version>```The validator must pass before creating a tag. It checks:- plugin and marketplace JSON version consistency- component counts in descriptions and READMEs- `docs/gateflow.index` coverage for every command, skill, and agent- root-level mirrors for every command-adjacent skill and agent file- a release note entry for the target version## Prep Workflow1. Count actual components:```bashfind plugins/gateflow/agents -maxdepth 1 -name '*.md' | wc -lfind plugins/gateflow/skills -maxdepth 2 -name 'SKILL.md' | wc -lfind plugins/gateflow/commands -maxdepth 1 -name '*.md' | wc -l```2. Update version strings:- `plugins/gateflow/.claude-plugin/plugin.json`- `.claude-plugin/marketplace.json`3. Update release-facing docs:- `README.md`- `plugins/gateflow/README.md`- `docs/gateflow.index`- `releases.md`4. Run validator and focused tests:```bashpython3 -m unittest tests/test_validate_gateflow.pypython3 tools/validate_gateflow.py --version <target-version>```5. Only after validation passes, tag and release:```bashgit tag v<target-version>gh release create v<target-version> --title "GateFlow v<target-version>" --notes-file <notes-file>```## Report Format```text---GATEFLOW-RESULT---STATUS: PASS | FAILVERSION: <target-version>INVENTORY: <agents> agents, <skills> skills, <commands> commands, <ip> IP, <boards> boardsFILES: <changed release-facing files>DETAILS: <summary or validation failures>---END-GATEFLOW-RESULT---```

Frequently asked questions