
from gateflow-plugin85
Validate GateFlow plugin manifests, docs, and release notes to ensure release readiness before tagging and publishing.
GF-Release provides a deterministic release-readiness workflow for GateFlow plugins. It validates plugin and marketplace JSON, checks docs/index coverage and root mirrors, verifies component counts (agents, skills, commands), and enforces the presence of a release note entry. The skill describes how to run the repository validator, perform inventory counts, update version strings and docs, and produce a machine-readable report for PASS/FAIL results.
Use GF-Release immediately before creating a Git tag or publishing a new plugin version. It is intended for maintainers preparing a release who need to ensure manifest consistency, docs coverage, and release notes are all present and correct. Run it during release-candidate checks or as a gated validation step in CI.
tools/validate_gateflow.py and unit tests (if present) for focused checks. (has_scripts=false in the fetch output but the skill documents the validation commands.)This skill is repository-focused and intended for autonomous agents that can run shell commands, read repository files, and edit text (examples: Claude Code, Copilot-style automation, or other agents with Bash/Read/Edit/Write capabilities).
GateFlow release readiness workflow that validates plugin manifests, marketplace metadata, docs coverage, and release notes before tagging. No bundled scripts — relies on an external validator (tools/validate_gateflow.py) in the GateFlow repo. SKILL.md is well-structured with clear steps, a version bump table, and a defined report format, but error handling guidance is thin.
Clean, non-malicious skill. Niche audience (GateFlow plugin devs only). No security concerns — standard git/gh CLI usage for releases.