菜单
Use when ready to publish a new version of cc-devflow npm package to npm registry, including version sync, changelog finalization, git tag creation, and publish verification.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/aiskillstore/marketplace --skill npm-release命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Maintain a portable task-state ledger for long, multi-step work. Use when a task spans many files, produces large logs, needs a reliable handoff, or requires traceable evidence without repeatedly loading full outputs. Creates concise state records and private evidence references with explicit limits, redaction checks, and retention guidance.
【收纳储物必看】装修前不会规划收纳，入住半年家变仓库？这个 Skill 内置装修课堂会员版「家居收纳储物方法」152篇原创知识库，专门讲收纳储物——收纳是家的骨架、柜子不是越多越好、收纳本质是把东西藏起来、收纳加勤快缺一不可。问玄关鞋柜怎么装、问厨房9个收纳位置、问衣柜衣帽间怎么做、问小户型怎么榨干每1平米、问收纳避坑和鸡肋神器，全部覆盖。适合正在装修、准备收纳规划、家里东西多总是乱、想做满墙柜/通顶柜/800库的业主。
【儿童房装修必看】家里有小孩、正准备要孩子、或想给儿童房做环保安全装修？这个 Skill 内置装修课堂知识库，专门讲"适童化"——儿童是最易受甲醛伤害的人群，儿童房必须实木/ENF/控总量。问儿童房怎么装环保、问儿童房墙面地面用什么、问儿童家具选实木还是人造板、问孩子学习/游戏专区怎么规划、问有娃家庭怎么防磕碰防污染，全部覆盖。适合家里有娃、备孕婚房、想装出健康儿童房的业主。
基于 SOC 职业分类
正在显示 SKILL.md
| name | npm-release |
| version | 1.1.0 |
| description | Use when ready to publish a new version of cc-devflow npm package to npm registry, including version sync, changelog finalization, git tag creation, and publish verification. |
| skill_class | maintenance |
| route_family | maintenance |
| reads | ["PLAYBOOK.md","CHANGELOG.md","references/git-commit-guidelines.md","../do-not-repeat-yourself/SKILL.md","references/checklist-contract.md"] |
PLAYBOOK.md, CHANGELOG.md, references/git-commit-guidelines.md, ../do-not-repeat-yourself/SKILL.md, and references/checklist-contract.md.git status --short, capture release_target_branch="$(git branch --show-current)", inspect current version and recent commits, then run npm whoami.npm-release 是内部维护 skill，不属于对外公开分发的五步 workflow。
Release is atomic: package.json, package-lock.json, CHANGELOG.md, release
commit, annotated tag, pushed branch, pushed tag, and npm registry version must
describe the same version.
Release skills must never auto-switch branches. If the current worktree is not already the user-confirmed release target, stop and ask for the correct release worktree/branch or create a separate release worktree without changing the main checkout.
Release commits follow references/git-commit-guidelines.md and run ../do-not-repeat-yourself/SKILL.md before staging.
npm whoami fails for the publish registry.| Type | Version Change | When |
|---|---|---|
patch | 2.4.3 -> 2.4.4 | Bug fixes, minor improvements |
minor | 2.4.4 -> 2.5.0 | Backward-compatible features |
major | 2.5.0 -> 3.0.0 | Breaking changes |
CHANGELOG.md, then update package.json and package-lock.json:npm version <patch|minor|major> --no-git-tag-version
npm run verify:publish
npm pack --dry-run
git add CHANGELOG.md package.json package-lock.json
git commit -m "$(cat <<'EOF'
chore(release): bump version to X.Y.Z
问题:
- 公开包版本、CHANGELOG 和发布标签需要落到同一个可追溯节点。
变更:
- 更新 package version 和 CHANGELOG 到 X.Y.Z。
- 为 npm publish 准备 release commit。
原因:
- release commit 把版本标记和说明绑定，避免 tag 指向不可解释的历史。
验证:
- npm run verify:publish
- npm pack --dry-run
风险:
- 中：版本、tag、registry 三者必须保持一致；失败时按本 skill 的恢复流程处理。
EOF
)"
git tag -a vX.Y.Z -m "$(cat <<'EOF'
Release vX.Y.Z - <brief title>
Main changes:
- Change 1
- Change 2
Full changelog: https://github.com/Dimon94/cc-devflow/blob/main/CHANGELOG.md
EOF
)"
git log --oneline -1
git show vX.Y.Z
git push origin "HEAD:${release_target_branch}"
git push origin vX.Y.Z
npm publish --dry-run
npm publish
npm view cc-devflow version
npx --yes cc-devflow@X.Y.Z --help
git push failure: keep local commit/tag, capture the remote error, and retry the exact branch/tag push when network/auth recovers.npm publish --dry-run failure: do not publish.npm publish failure: capture registry output; do not delete local commit/tag to hide the failed release state.npm unpublish cc-devflow@X.Y.Z
git tag -d vX.Y.Z
git push origin :refs/tags/vX.Y.Z
git revert HEAD
After npm's unpublish window, publish a new patch instead.
package.json, package-lock.json, CHANGELOG.md, release commit, tag, and npm registry version match.npm publish succeeded, or the registry blocker is captured after dry-run prevented real publish.npm view and npx --yes cc-devflow@X.Y.Z --help.