A release command that takes a pull request—a proposed code change—from review through npm publication, with npm being the package registry for JavaScript projects.

Use it to release a specified pull request, update its version and changelog when needed, merge the required branches, and monitor the publishing workflow.

It organizes the branch merges, version checks, changelog updates, tagging, and automated publishing involved in a package release.

How atikk-co-jp/notion-mcp-server configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to atikk-co-jp/notion-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/atikk-co-jp/notion-mcp-server/main/.claude/commands/npm-release.md

Clone the repo

git clone --depth 1 https://github.com/atikk-co-jp/notion-mcp-server

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/atikk-co-jp/notion-mcp-server/npm-release/github.svg)](https://agentmods.dev/commands/atikk-co-jp/notion-mcp-server/npm-release)

Your own site

<a href="https://agentmods.dev/commands/atikk-co-jp/notion-mcp-server/npm-release"><img src="https://agentmods.dev/badge/commands/atikk-co-jp/notion-mcp-server/npm-release/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/atikk-co-jp/notion-mcp-server/npm-release"><img src="https://agentmods.dev/badge/commands/atikk-co-jp/notion-mcp-server/npm-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,232 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00018	$0.01232
Opus 5	$0.00009	$0.00616
Sonnet 5	$0.00004	$0.00246
Haiku 4.5	$0.00002	$0.00123

Measured 10d ago against content hash a6ab9ea0b788, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

npm-release scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/npm-release.md · 111 lines

How it starts

The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.

npm Release - 完全なリリースフロー

Context

このコマンドは以下のリリースワークフローを自動化します：

指定されたPRをdevelopにマージ
develop → main向けのリリースPRを作成・マージ
リリースタグを作成してpublish.ymlをトリガー
GitHub Actionsの完了を監視

リリースワークフロー: @.github/workflows/publish.yml

Task

PR #$1 をリリースする

Steps

1. 事前確認

指定されたPR（#$1）の状態を確認（gh pr view $1）
PRがdevelopブランチ向けであることを確認
CIが通っていることを確認
package.jsonから現在のバージョンを取得

2. バージョン・CHANGELOG確認

PRの変更内容を確認し、適切なバージョン番号を決定（semver準拠）
- 破壊的変更: メジャーバージョンを上げる
- 機能追加: マイナーバージョンを上げる
- バグ修正・ドキュメント: パッチバージョンを上げる
package.jsonのバージョンが更新されているか確認
CHANGELOG.mdに該当バージョンの記載があるか確認

不足がある場合は、PRブランチに以下を追加コミット：

package.jsonのバージョン更新
CHANGELOG.mdの該当バージョンセクション追加（必ず英語で記載）

# PRブランチをチェックアウト
gh pr checkout $1

# バージョン更新（必要な場合）
npm version <patch|minor|major> --no-git-tag-version

# CHANGELOG.md更新（必要な場合）
# 形式例:
# ## [0.x.x] - YYYY-MM-DD
# ### Added
# - New feature description
# ### Fixed
# - Bug fix description

# コミットしてプッシュ
git add package.json CHANGELOG.md
git commit -m "chore: bump version to <version>"
git push

CIが再度通ることを確認

3. PRマージ（develop向け）

PRをマージ（gh pr merge $1 --squash）
ローカルのdevelopを最新化（git checkout develop && git pull origin develop）

4. リリースPR作成（develop → main）

mainブランチを最新化（git fetch origin main）

develop → main向けのPRを作成

gh pr create --base main --head develop --title "Release v<version>" --body "## Changes\n\n<develop→mainの差分サマリー>"

PRのCIが通るのを待機

5. リリースPRマージ

CIが通ったらPRをマージ（gh pr merge <pr-number> --merge）
ローカルのmainを最新化

6. リリースタグ作成

package.jsonのバージョンを確認

GitHub Releaseを作成（これがpublish.ymlをトリガー）

gh release create v<version> --target main --title "v<version>" --notes "<リリースノート>"

7. GitHub Actions監視

publish.ymlワークフローの実行を確認（gh run list --workflow=publish.yml --limit=1）
ワークフローの完了を待機（gh run watch <run-id>）
成功を確認

Constraints

PRがdevelop向けでない場合はエラーで中止
CIが失敗している場合はマージしない
タグバージョンはpackage.jsonのバージョンと一致させる（publish.ymlの検証に必要）
package.jsonのバージョンが更新されていない場合は、PRマージ前に必ず更新する
CHANGELOG.mdに該当バージョンの記載がない場合は、PRマージ前に必ず追加する
CHANGELOG.mdは必ず英語で記載する（日本語は不可）
リリースノートはCHANGELOG.mdの該当バージョンの内容を使用する
mainへのマージは--merge（squashではない）を使用してコミット履歴を保持
GitHub Actionsが失敗した場合は原因を報告

Read the full file on GitHub · 111 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

10d ago First seen · 111 lines · 18 tokens per session scan A a6ab9ea0b788

Subscribe to this mod's changes

npm-release is a command published in the GitHub repository atikk-co-jp/notion-mcp-server (1 stars, last pushed 7mo ago), licensed MIT. It adds 18 tokens to every session and 1,232 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Git and workflow Releases

land

Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).

gmickel/flow-next · 25 tokens

release-notes

Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.

OpenHands/extensions · 44 tokens

ship

Ship is the operational release-prep flow for a connected project repo.

robotaitai/project-bedrock · 0 tokens

release-plan

A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.

alisunstar/OpenSunstar · 0 tokens

create-pr

Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.

dsswift/ion · 28 tokens

release

Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.

terrene-foundation/kailash-coc-claude-py · 0 tokens

notion-mcp-server: Command for Claude Code