Agent skill · software engineering · aiskillstore
npm-release
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.
Why this skill is useful
Adds a detailed npm release workflow with specific commands and procedures that the AI wouldn't reliably generate on its own.
What it needs
Requires npm installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
NPM Release Workflow Quick Start 1. Read PLAYBOOK.md, CHANGELOG.md, references/git-commit-guidelines.md, ../do-not-repeat-yourself/SKILL.md, and references/checklist-contract.md. 2. Confirm the current worktree and branch are the user-approved release target. 3. Run git status --short, capture releasetargetbranch="$(git branch --show-current)", inspect current version and recent commits, then run npm whoami. 4. Stop before real publish when git state, branch target, version conclusion, changelog, or npm auth is not proven. npm-release 是内部维护 skill，不属于对外公开分发的五步 workflow。 Release Law 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. Stop Conditions Current branch is not the user-confirmed release target. Uncommitted changes exist before release preparation. Unpushed commits exist and the user has not approved releasing from this branch state. npm whoami fails for the publish registry. The release is pre-release/beta and no adaptation plan exists. Release Flow 1. Choose semver level: 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 2. Update CHANGELOG.md, then update package.json and package-lock.json: 3. Verify: 4. Commit: 5. Tag: 6. Verify commit and tag: 7. Push and publish: Failure Policy git push failure: keep local commit/tag, capture the remote error, and retry the exact branch/tag push when network/auth recovers. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/npm-release