菜单
Commit, version bump, tag, and publish a release. Use when the user says 'ship', 'release', 'publish', 'bump version', 'tag a release', 'push a new version', 'let's ship this', 'cut a release', 'publish to PyPI', or any variation of wanting to commit and deploy a library release.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/kklimuk/claude-starter --skill ship命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Create well-structured git commits from the current working tree. Use when the user says 'commit', 'save my work', 'let's commit this', 'make a commit', or any variation of wanting to commit code to git.
Commit, version bump, tag, and publish a release. Use when the user says 'ship', 'release', 'publish', 'bump version', 'tag a release', 'push a new version', 'let's ship this', 'cut a release', 'publish to npm', or any variation of wanting to commit and deploy a library release.
PR-scoped code review — reviews what changed on the current branch. Use when the user says 'review', 'code review', 'review my PR', 'review my changes', 'look at my diff', 'what could this break', or any variation of wanting feedback on recent changes. Do NOT use for full codebase audits — that's /codebase-review.
| name | ship |
| description | Commit, version bump, tag, and publish a release. Use when the user says 'ship', 'release', 'publish', 'bump version', 'tag a release', 'push a new version', 'let's ship this', 'cut a release', 'publish to PyPI', or any variation of wanting to commit and deploy a library release. |
Commit changes, bump the version, tag, and push to trigger a PyPI publish.
Run uv run ruff check ., uv run ruff format --check ., and uv run pytest. All three must pass before proceeding. If any fails, stop and fix — do not skip checks (no --no-verify).
git status and git diff to understand what changed.git log --oneline -10 to match the existing commit message style./commit to do that cleanly, then return.git add -A) and commit with a message that follows the project convention from CLAUDE.md.Always update CLAUDE.md and README.md if conventions, file structure, or invariants changed in this release.
Ask the user whether this is a major, minor, or patch change. Use these guidelines to suggest one:
x.0.0): Breaking API changes — removed exports, renamed functions, changed signatures or return types that consumers depend on. If still on 0.x.0, minor bumps may carry breaking changes by convention.0.x.0): New features, new exports, new options — anything additive.0.0.x): Bug fixes, doc updates, internal refactors with no API change.Present the suggestion but let the user decide.
pyproject.toml ([project] version = "...").pyproject.toml.chore: bump version to {new_version}.git tag -a v{new_version} -m "v{new_version}: <one-line summary of the release>". The annotation should be enough that someone reading git show v{new_version} understands what shipped.git push && git push --tagsThis triggers .github/workflows/publish.yml, which publishes to PyPI via OIDC trusted publishing.
After pushing, report:
v{new_version}).gh run list --workflow=publish.yml --limit=1.--no-verify). If it fails, fix the issue and try again.git push or git push --tags.v{version} (e.g. v0.10.0), NOT just the number.