release
Release
Cut a GitHub release from a bump keyword (major / minor / patch, optionally
beta, or stable), with an explicit version number as escape hatch. Nothing is
hardcoded: repo, build command and CI behavior are detected, with optional
overrides in a ## Releasing section of the project's CLAUDE.md / AGENTS.md
(see the end of this file). Ask the user only when detection is ambiguous.
The contract. Publishing is CI-driven: a release workflow triggers on the
created release, stamps the versions (repo files stay at their placeholder,
commonly 0.0.0, never committed back), builds and publishes; the release's
prerelease flag picks the dist-tag / target environment. So this skill never
bumps versions, creates commits, pushes tags, or publishes. Its only remote
mutation is gh release create in step 6, which must not run before the user
confirms in step 5.