| name | prepare-release |
| description | Prepare a wave-level genblaze release — scope version bumps and dependency-floor drift with tools/prepare_release.py, apply them, gate with make pre-release, and open a release PR. Cannot tag or publish. Use before cutting a new CHANGELOG wave (as opposed to /release-check, which gates one already-decided package version). |
| allowed-tools | Bash(git add:*) Bash(git commit:*) Bash(git checkout:*) Bash(git switch:*) Bash(git push:*) Bash(git status:*) Bash(git diff:*) Bash(git log:*) Bash(git show:*) Bash(python3:*) Bash(make pre-release:*) Bash(make ts-types:*) Bash(gh pr:*) Read Grep Edit |
Prepare a release wave — $ARGUMENTS
Safety boundary: the allowed-tools list above deliberately has no git tag,
gh release, twine upload, or make post-release. This skill cannot tag or publish
anything — without a git tag step there is no tag to push, and without gh release
or twine there is nothing to trigger .github/workflows/release.yml. It goes as far
as a merge-ready release PR and stops. Tagging, releasing, and post-release
verification are human commands, emitted (not run) at the end.
This is a thin driver over tools/prepare_release.py,
which does the actual bookkeeping (dynamic package discovery, version bumps, dependency
floor sync, reserved-core-version guard — see its module docstring). For what a wave
release actually IS (versioning policy, the publish pipeline graph, tag-naming
convention) see RELEASING.md — this skill does not restate
it. For gating one already-decided package version one at a time, use
instead; this skill operates at the wave level across every package at once.
