菜单
Cut a new release for this repository. Use when asked to bump a major, minor, or patch version, publish to npm, create or push a git tag, or walk through the repo's release process. Prefer the built-in /release major|minor|patch command in this repo.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/championswimmer/pi-context-usage --skill release命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | release |
| description | Cut a new release for this repository. Use when asked to bump a major, minor, or patch version, publish to npm, create or push a git tag, or walk through the repo's release process. Prefer the built-in /release major|minor|patch command in this repo. |
| compatibility | Requires a clean git working tree, git push access to the repository, and npm Trusted Publishing configured for this package/workflow. |
Use this skill when the user wants to publish a new version of this package.
In this repository, prefer the automated slash command:
/release major
/release minor
/release patch
The /release extension command is the canonical release flow for this repo.
It prepares the release commit/tag and lets GitHub Actions publish via npm Trusted Publishing instead of asking the model to manually stitch together shell commands.
/release doesThe command performs this workflow:
major, minor, or patchpackage.json to determine the current package name and versionnpm run test:mocknpm version <level> --no-git-tag-versionrelease: vX.Y.ZvX.Y.Zpi-context-usagepackage.jsonpackage-lock.jsonvX.Y.Z.github/workflows/publish.ymlnpm run test:mockpublish.ymlThe GitHub Actions publish workflow is intentionally tolerant of duplicate publishes. If the version is already on npm for any reason, the tag-triggered workflow should skip the duplicate publish instead of failing.
Use /release <level> when the user asks any of the following:
If the user only wants to inspect or explain the process, describe it instead of running it.
Before releasing, make sure these conditions hold:
If any preflight check fails, stop and show the error instead of forcing the release.
/release major, /release minor, or /release patch.patch: backwards-compatible bugfix releaseminor: backwards-compatible feature releasemajor: breaking changesgit status before retrying.If /release is unavailable for some reason, use this manual fallback carefully:
npm run test:mock
npm version <major|minor|patch> --no-git-tag-version
git add package.json package-lock.json
git commit -m "release: vX.Y.Z"
git tag vX.Y.Z
git push origin <branch>
git push origin vX.Y.Z
Replace X.Y.Z with the bumped version and <branch> with the current branch.
If the release workflow changes, keep these in sync:
src/index.ts release command implementationsrc/release.ts.github/workflows/publish.ymlREADME.md