release-bumper

Topics in the source

• Release Bumper
• Arguments
• Helper Interface
• Workflow
• Safety and Completion

If a slash or dollar invocation already added these instructions to the conversation, follow them directly. In that case, do not invoke this skill again through a skill tool. Release one package or several packages with version bumps, changelog entries, commits, and tags. A non-dry-run invocation authorizes the repository-local version edits, changelogs, commits, and annotated tags defined by this workflow. Do not add a generic confirmation gate after the agent derives the release plan. Ask only when an unresolved package selection or dependency-range policy changes the release set or approach. GitHub release creation remains a separate external write governed below. packages: optional package names or directories. Omit in a single-package repository. version: optional explicit semver. Valid only for one user-selected package. --beta: create or advance a -beta.X prerelease. --dry-run: preview without modifying files, committing, or tagging. Resolve from this SKILL.md. Keep helper stdout as JSON and diagnostics on stderr. The read-only discovery output has schemaVersion: 2. It reports package identity, complete per-package changedFiles, workspace edges and declared ranges, previous-

This is an excerpt. Refer to the complete source and its current requirements.