菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/davila7/claude-with-skills --skill tag-version命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Explains code in plain language for someone unfamiliar with the programming language. Use when asked to explain code, walk through logic, describe what a function does, or when the user says "explain this" or "walk me through this".
Summarizes uncommitted git changes in a concise machine-readable format. Use in CI pipelines, scripts, or headless invocations where the output will be piped or captured.
Explains what a skill is and demonstrates that skills are working. Use when testing skills, when asked about skills, or when asked to demonstrate how skills work.
基于 SOC 职业分类
正在显示 SKILL.md
| title | tag-version |
| name | tag-version |
| description | 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. |
| disable-model-invocation | true |
| argument-hint | ["version|patch|minor|major"] |
| allowed-tools | Bash(npm version *) Bash(git tag *) Bash(git log *) Bash(cat package.json) |
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: /tag-version patch or /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 /publish to push it to origin and create the GitHub release."
Do not push. The publish skill handles pushing.