メニュー
Bump package version, create a git tag, and publish to npm. Use when the user asks to "publish", "release", "bump version", "npm publish", "create a release", "tag and publish", "/npm-publish", "new version", or any variation of releasing/publishing the package to npm.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Bump the npm package version, commit, and create a PR for merging before publishing. Use when the user asks to "bump version", "bump the version", "prepare a release", "version bump", "/bump-version", or when `/npm-publish` is invoked but the version hasn't been bumped yet. This skill ensures the version is incremented, committed, and merged to main via PR before publishing.
Create git commits from staged changes. Use when the user asks to commit, make a commit, git commit, save changes, or any variation of committing code. Triggers on requests like "commit this", "commit my changes", "/commit", or "make a commit".
| name | npm-publish |
| description | Bump package version, create a git tag, and publish to npm. Use when the user asks to "publish", "release", "bump version", "npm publish", "create a release", "tag and publish", "/npm-publish", "new version", or any variation of releasing/publishing the package to npm. |
Bump the version in package.json, create a git tag, and publish @procurementexpress.com/mcp to npm.
Run these in parallel:
git status — working tree must be clean (no uncommitted changes)git branch --show-current — must be on main branchnpm test — all tests must passIf any check fails, stop and tell the user what to fix.
Version check: Compare the current version in package.json against the latest published version:
npm view @procurementexpress.com/mcp version
If the versions match (not yet bumped), stop and tell the user to run /bump-version first to bump the version, commit, and merge a PR to main before publishing.
Ask the user for their npm auth token. They can find or generate one at: https://www.npmjs.com/settings/~/tokens
Store it for use in the publish step. Never commit or log the token.
Run these commands sequentially:
# Create git tag for current version
git tag -a "v$(node -p "require('./package.json').version")" -m "v$(node -p "require('./package.json').version")"
# Push the tag to remote
git push origin --tags
# Build and publish with auth token
npm publish --//registry.npmjs.org/:_authToken=<npm_token>
If publish fails with 404 or auth error:
@procurementexpress.comAfter publishing, confirm success:
npm view @procurementexpress.com/mcp version
Report the published version and the npm package URL: https://www.npmjs.com/package/@procurementexpress.com/mcp