.NET MAUI Release Readiness
dotnet/maui
Produces evidence-backed ship-readiness verdicts for .NET MAUI Servicing Releases and Previews, and drafts public-safe release handoff pages from the result.
Pre-release readiness check for the voxglitch plugin, run before submitting a version to the VCV Rack library.
Install Release Check
$ npx skills add clone45/voxglitch --skill release-check -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install clone45/voxglitch release-check --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/clone45/voxglitch.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/release-check .claude/skills/release-check && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "release-check" agent skill from https://github.com/clone45/voxglitch/tree/master/.claude/skills/release-check into .claude/skills/release-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-check", 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.
$skill-installer install https://github.com/clone45/voxglitch/tree/master/.claude/skills/release-checkType 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.
$ npx skills add clone45/voxglitch --skill release-check -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install clone45/voxglitch release-check --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/clone45/voxglitch.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/release-check .agents/skills/release-check && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release-check" agent skill from https://github.com/clone45/voxglitch/tree/master/.claude/skills/release-check into .agents/skills/release-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-check", 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.
$ npx skills add clone45/voxglitch --skill release-check -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install clone45/voxglitch release-check --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/clone45/voxglitch.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/release-check .cursor/skills/release-check && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "release-check" agent skill from https://github.com/clone45/voxglitch/tree/master/.claude/skills/release-check into .cursor/skills/release-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-check", 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.
$ gemini skills install https://github.com/clone45/voxglitch.git --path .claude/skills/release-check--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add clone45/voxglitch --skill release-check -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install clone45/voxglitch release-check --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/clone45/voxglitch.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/release-check .gemini/skills/release-check && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "release-check" agent skill from https://github.com/clone45/voxglitch/tree/master/.claude/skills/release-check into .gemini/skills/release-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-check", 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.
$ gh skill install clone45/voxglitch release-checkInstalls 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).
$ npx skills add clone45/voxglitch --skill release-check -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/clone45/voxglitch.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/release-check .github/skills/release-check && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "release-check" agent skill from https://github.com/clone45/voxglitch/tree/master/.claude/skills/release-check into .github/skills/release-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-check", 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.
$ npx skills add clone45/voxglitch --skill release-check -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install clone45/voxglitch release-check --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/clone45/voxglitch.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/release-check .opencode/skills/release-check && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "release-check" agent skill from https://github.com/clone45/voxglitch/tree/master/.claude/skills/release-check into .opencode/skills/release-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-check", 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-check- GitHub stars
- 131
- Token cost
- ~781 tokens
- SKILL.md length
- 359 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Pre-release readiness check for the voxglitch plugin, run before submitting a version to the VCV Rack library.
- Preparing a release
- Calls python3
- Checking release readiness
- Asked to run the prerelease check
What it does
Release Check is an agent skill from clone45/voxglitch. Pre-release readiness check for the voxglitch plugin, run before submitting a version to the VCV Rack library. Verifies the tree is clean and pushed, no debug switches or stray prints ship, every TU compiles, static analysis matches the baseline, manual links resolve, and the version was bumped — then preps the library issue posting. Use when preparing a release, checking release readiness, or when asked to run the prerelease check.
Its SKILL.md is about 780 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 Product & Project Management, covering Feature launches and release readiness and Static analysis and SAST. The licence is GPL-3.0.
When your agent uses it
- Preparing a release
- Checking release readiness
- Asked to run the prerelease check
Example prompts
- “/release-check”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit 0baadb5. 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:
python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Release Check loads about 781 tokens when it runs. Until then it costs about 113 tokens; SKILL.md has 359 words of instructions outside code blocks.
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.
SKILL.md
The full file from clone45/voxglitch at commit 0baadb5, republished under its GPL-3.0 licence (© clone45). 359 words, ~781 tokens.
Download SKILL.mdSave it as
.claude/skills/release-check/SKILL.md (or your agent's skills folder).- name
- release-check
- description
- Pre-release readiness check for the voxglitch plugin, run before submitting a version to the VCV Rack library. Verifies the tree is clean and pushed, no debug switches or stray prints ship, every TU compiles, static analysis matches the baseline, manual links resolve, and the version was bumped — then preps the library issue posting. Use when preparing a release, checking release readiness, or when asked to run the prerelease check.
Voxglitch release check
All checks live in one script — do not re-derive them by hand:
python3 scripts/release_check.py --module "Piano Roll" --kind update--module/--kind new|updateshape the issue title (New module: Piano Roll (updated)); omit both for a plain plugin update.--skip-buildskips the compile sweep and cppcheck for a fast re-run after fixing a non-code finding.
Rack SDK version lives in FOUR places and must move together: the
rack-sdk-version env in .github/workflows/build-macos.yml,
build-linux.yml and build-windows.yml, plus the local ../Rack-SDK this
check compiles against. Skew between them is how the Linux workflow stayed
red for eight months (the CI image had a pre-2.6 SDK while local and macOS
had 2.6.4, so isKeyCommand built here and failed there). When bumping the
SDK, change all three workflows and refresh the local SDK in the same
sitting.
--version-okpasses the version-bump check when Bret has confirmed the current version is meant to cover source commits made since it changed. Only pass it on his explicit say-so.- The compile sweep needs the Rack SDK; it defaults to
../Rack-SDK, override withRACK_DIR=.... Full run takes 2-4 minutes.
The script prints JSON and exits non-zero if anything failed. Report the
results as a short pass/fail table, quoting the detail of any failure.
When everything passes it writes the library posting to
docs/releases/library_issue_v<version>.md (title + repo URL + version +
full commit hash — the exact format of past submissions). Point Bret at the
file. Never post the issue yourself — library submissions, like all of
cschol's tickets, are written and posted by Bret personally.
Show full SKILL.md (113 more words)Show less
What it checks, for context (the script is authoritative):
- on master, tree clean (
.claude/anddocs/releases/exempt), pushed - no stray
printf/cout/cerr/fprintfoutside vendored code #define DEVELOPMENTcommented out invgLib-2.0/helpers/Debugging.hpp, and no-DDEVELOPMENTin the Makefile (either ships VBUG logging to every user's Rack log)- every TU compiles with full codegen and
-Wall -Wextra(warnings fail —-fsyntax-onlyis not used because it misses codegen-time warnings) scripts/static_analysis/analyze.pyreports nothing beyond the baselineplugin.jsonversion changed since the lastsrc/commit- every module's
manualUrlresolves (HEAD request). A missing manualUrl is warning-only — fourteen legacy modules have never had one (Bret's call, 2026-08-29) — but a set-and-broken or non-http URL still fails. - HEAD's commit exists on GitHub
© clone45, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/release-check of clone45/voxglitch.
Open the folder on GitHubat commit 0baadb5
Compare with similar skills
Release Check 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Release Check this skillclone45/voxglitch | 131 | — | ~781 | Automated safety check: Pass | GPL-3.0 | |
| .NET MAUI Release Readinessdotnet/maui | 23k | — | ~15k | Automated safety check: Pass | MIT | |
| Release ValidationMesh-LLM/mesh-llm | 3.5k | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Final Release Reviewopenai/openai-agents-python | 30k | — | ~5.4k | Automated safety check: Pass | MIT | |
| Final Release Reviewopenai/openai-agents-js | 3.9k | — | ~4k | Automated safety check: Pass | MIT | |
| Acceptance Demo GeneratorChachamaru127/claude-code-harness | 3.2k | — | ~3.4k | Automated safety check: Notes | MIT |
Similar skills
- Official
Release Validation
Mesh-LLM/mesh-llm
A skill your agent uses when validating a MeshLLM release candidate or current HEAD against the last GitHub release, assembling the canonical feature/fix/modification inventory, testing locally…
- Official
Final Release Review
openai/openai-agents-python
Assess a Python SDK release candidate or release plan against the previous release and recommend ship or block.
- Official
Final Release Review
openai/openai-agents-js
Assess a JS SDK release candidate or release plan against the previous release and recommend ship or block.
Acceptance Demo Generator
Chachamaru127/claude-code-harness
Renders a single HTML page showing each acceptance criterion as verified or not, with a ship, wait, or reject recommendation for non-engineers.
Schematic
blader/schematic
Reverse engineer a detailed product and technical specification document from a git branch's implementation.
More from clone45/voxglitch
Vcv Static Analysis
clone45/voxglitch
Run the VCV Rack library's static-analysis check on voxglitch locally, before submitting a release.
Related
Categories
Questions about Release Check
What does Release Check do?
Pre-release readiness check for the voxglitch plugin, run before submitting a version to the VCV Rack library. Release Check is an agent skill from clone45/voxglitch. Pre-release readiness check for the voxglitch plugin, run before submitting a version to the VCV Rack library.
When should I use Release Check?
Release Check fits situations like: preparing a release; checking release readiness; asked to run the prerelease check.
How do I install Release Check in Claude Code?
Run `npx skills add clone45/voxglitch --skill release-check -a claude-code`. Or copy the skill folder (.claude/skills/release-check in clone45/voxglitch) into .claude/skills/release-check in your project. Claude Code loads it when a task matches its description.
How do I install Release Check in Codex?
Run `npx skills add clone45/voxglitch --skill release-check -a codex`. Or copy the skill folder (.claude/skills/release-check in clone45/voxglitch) into .agents/skills/release-check in your project. Codex loads it when a task matches its description.
Can I use Release Check 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 clone45/voxglitch --skill release-check -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-check, .gemini/skills/release-check, .github/skills/release-check and .opencode/skills/release-check in your project.
What does Release Check need to run?
Going by SKILL.md and its folder, Release Check needs the command-line tools its instructions call (python3). Our summary lists: Python 3.
Does Release Check access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Release Check 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 Check use?
Release Check is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Release Check use?
About 781 tokens (SKILL.md is roughly 3.1k 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 Check?
Skills that share tags, products or a category with Release Check: .NET MAUI Release Readiness (dotnet/maui, 23k stars), Release Validation (Mesh-LLM/mesh-llm, 3.5k stars), Final Release Review (openai/openai-agents-python, 30k stars) and Final Release Review (openai/openai-agents-js, 3.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release Check?
clone45 (a GitHub user) maintains it in clone45/voxglitch, which has 131 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 14, 2026.
Source: clone45/voxglitch on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.