Bump the package version and create an annotated git tag. Accepts a semantic version number (1.2.0) or a bump type (patch, minor, major). Does not push — use the publish skill to push. Use as part of a release workflow.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Bump the version and create an annotated git tag for $ARGUMENTS.
If $ARGUMENTS is empty, stop and tell the user: "Provide a version or bump type — for example: /release-plugin:tag-version patch or /release-plugin:tag-version 1.2.0."
Inspect the current version:
!cat package.json 2>/dev/null | grep '"version"' | head -1 || echo "no package.json found"
If $ARGUMENTS is a semantic version string matching the pattern X.Y.Z (e.g., 1.2.0, 0.9.1), use it directly as the new version.
If $ARGUMENTS is patch, minor, or major, run:
npm version $ARGUMENTS --no-git-tag-version
This updates package.json without creating a git tag. Read the new version from package.json after the command runs:
cat package.json | grep '"version"'
If npm version was used to update package.json, stage the change:
git add package.json package-lock.json
git commit -m "Bump version to v$VERSION"
If the version was provided as a literal semver string, update package.json manually: edit the "version" field to the new value, then stage and commit it.
git tag -a v$VERSION -m "Release v$VERSION"
Run git describe --tags --abbrev=0 and show the output. Confirm: "Tag v$VERSION created. Run /release-plugin:publish to push it to origin and create the GitHub release."
Do not push. The publish skill handles pushing.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Write an Architecture Decision Record (ADR) document for a technical decision. Use when documenting a technical choice, architectural decision, or design decision.
The English summary is being prepared. Showing the original description.
REST API design conventions for this codebase. Use when writing or reviewing API endpoints, route definitions, response formatting, or client code that calls the API.
The English summary is being prepared. Showing the original description.
Automatically format code files after every edit using Prettier and ESLint. Active in the background whenever Claude edits a file. Formatting is silent — no prompts, no output unless a formatter fails. Use when you want consistent formatting enforced automatically during a coding session.
The English summary is being prepared. Showing the original description.
Create a git branch named after a GitHub issue.
The English summary is being prepared. Showing the original description.
Draft the changelog entry for all unreleased commits in Keep a Changelog format. Groups commits into Added, Changed, Fixed, Removed, and Security. Use before releasing a new version or when updating CHANGELOG.md.
The English summary is being prepared. Showing the original description.
Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.
The English summary is being prepared. Showing the original description.