菜单
Run the complete release workflow: changelog entry, version bump, git tag, and GitHub release. Invokes changelog-entry, tag-version, and publish in sequence. Use when releasing a new version of the project.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/davila7/claude-with-skills --skill release命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 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 | release |
| name | release |
| description | Run the complete release workflow: changelog entry, version bump, git tag, and GitHub release. Invokes changelog-entry, tag-version, and publish in sequence. Use when releasing a new version of the project. |
| disable-model-invocation | true |
| argument-hint | [version|patch|minor|major] |
| allowed-tools | Bash(git tag *) Bash(git log *) Bash(git status) Bash(git describe *) Bash(npm version *) Bash(gh release *) |
Run the complete release workflow for $ARGUMENTS (e.g., 1.2.0, patch, minor, major).
If $ARGUMENTS is empty, stop and tell the user: "Provide a version or bump type — for example: /release patch or /release 1.2.0."
Check the current state before doing anything:
!git status --short 2>&1
!git describe --tags --abbrev=0 2>/dev/null && echo "latest tag found" || echo "no tags yet"
If the working tree is dirty (uncommitted changes shown above), stop and tell the user to commit or stash their changes before running the release workflow. A release must start from a clean state.
Run /changelog-entry to generate the changelog entry for all commits since the last tag.
Review the output carefully. Ask the user: "Does this changelog entry look accurate? Type 'yes' to continue or 'edit' to open CHANGELOG.md first."
If the user says 'edit', open CHANGELOG.md and wait for them to confirm they are done editing before continuing.
Run /tag-version $ARGUMENTS to bump the version in package.json and create the annotated git tag.
Confirm the tag was created by showing the output of git describe --tags --abbrev=0.
Run /publish to push the tag to origin and create the GitHub release.
Report the release URL returned by /publish. Tell the user the release is complete.
If any step fails, stop immediately and report which step failed and what the error was. Do not attempt to continue after a failure.
