Publish npm Version Agent Skill

>- package.json version, propagates it to every workspace package in lockstep, merges the PR, the `Publish to npm` workflow runs automatically and ships the new version to npm under dist-tag `latest`, plus a matching GitHub Release with auto-generated notes. Use when a maintainer asks to "cut the next minor", "bump to the next version", "open a release PR", or "prepare a publish PR".

853 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/prisma/prisma --skill publish-npm-version

The instruction itself

6 sections, as written by the author

Publish next npm version

Audience

Maintainers who can push branches and open PRs. Invoke this locally, not as a

GitHub Action — a PR opened by a workflow's GITHUB_TOKEN does not trigger CI,

which defeats the point of a reviewable release.

Background reading

Read docs/oss/versioning.md first — it is the

policy this skill mechanises: the root-package.json source of truth, the

lockstep guarantee, the dist-tag convention, and the full procedure (this skill

is the "open the bump PR" step; merging the PR is the publish trigger — there

is no separate dispatch step).

Pre-flight

Confirm you can fetch from origin (git fetch origin main succeeds). The skill

works in a fresh worktree off origin/main, so your current worktree is left

undisturbed.

Steps

Fresh worktree off origin/main:

   git fetch origin main
   git worktree add -b chore/release-vNEXT ../release-vNEXT origin/main
   cd ../release-vNEXT
   pnpm install --frozen-lockfile

Bump. pnpm bump-minor reads the root version at HEAD, computes the next

minor (0.2.0 → 0.3.0), stamps every workspace package.json in

lockstep (rewriting internal workspace: deps to the new version), and

regenerates pnpm-lock.yaml to match.

Sanity-check the bump is clean and complete. The diff must include

pnpm-lock.yaml — CI installs with --frozen-lockfile, so a bump without the

lockfile fails every CI job at the install step:

   git diff --stat                      # every workspace package.json + pnpm-lock.yaml
   pnpm check:publish-deps              # no workspace:/catalog: leaks, exact internal pins

Commit with the release title and dual DCO sign-off, then push and open the PR:

   git commit -am "chore(release): v<version>"
   git push -u origin chore/release-vNEXT
   gh pr create --base main --title "chore(release): v<version>" \
     --body "Release v<version>. Merging this triggers the Publish to npm workflow."

Hand off. Tell the maintainer the PR is open and that merging it ships

<version> to npm under latest (via OIDC trusted publishing) and cuts a

GitHub Release with auto-generated notes. Do not merge it yourself unless asked.

What this skill does NOT do

Patches / old minors. There are no patch releases of older minors

(versioning.md § pre-1.0). This skill only advances the latest minor.

The publish itself. That is the Publish to npm workflow, triggered by the

merge — never run pnpm publish by hand for a normal release.

Release notes authoring. The GitHub Release notes are auto-generated

(gh release create --generate-notes) by the workflow; there is no committed

release-notes file to write.

Other skills for the same job

different authors, same section of the catalogue

MCP Builder

by anthropics

vendor ×13

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens

Finishing A Development Branch

by ZhanlinCui

×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Vercel React Native Skills

by vercel-labs

vendor ×6

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

39k tokens

Vercel React Best Practices

by ratacat

×5

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

1k tokens

How to use it

Copy the folder

Take prisma/publish-npm-version from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.

Install what it needs

The instructions reference npm. Without those the skill loads but fails at the first command.