plugins/gateflow/skills/gf-release/SKILL.md
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.
npx skillsauth add codejunkie99/gateflow-plugin gf-releaseInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
allowed-tools:
Use this workflow before tagging or publishing GateFlow.
2.5.0If 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 |
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:
docs/gateflow.index coverage for every command, skill, and agentfind 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
plugins/gateflow/.claude-plugin/plugin.json.claude-plugin/marketplace.jsonREADME.mdplugins/gateflow/README.mddocs/gateflow.indexreleases.mdpython3 -m unittest tests/test_validate_gateflow.py
python3 tools/validate_gateflow.py --version <target-version>
git tag v<target-version>
gh release create v<target-version> --title "GateFlow v<target-version>" --notes-file <notes-file>
---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---
testing
Testbench verification best practices and patterns. This skill should be used when the user needs testbench architecture guidance, verification methodology, or wants to write professional-quality testbenches. Example requests: "testbench best practices", "how to structure TB", "verification patterns"
testing
Primary SystemVerilog/RTL orchestrator for GateFlow. Routes to specialist agents, runs verification, and iterates until working. Use when the user wants to create, test, fix, or implement any RTL design — FIFO, UART, AXI, state machines, or any digital hardware module.
development
Terminal visualization for GateFlow codebase maps. Renders module hierarchies, FSM state diagrams, and module detail cards as interactive ASCII/Unicode art. Example requests: "visualize the codebase", "show hierarchy", "show FSM", "show module detail"
tools
Summarize Verilator, lint, or simulation output into a readable, actionable format. Use when the user wants to understand build output, lint errors, or simulation results from a Verilator or EDA tool run.