Skip to content
Get packs

Guide · Agent skill

How to use the Publish Next Prisma npm Version agent skill

Updated · written with AI from the project's own documentation and checked against our catalogue data

The publish-npm-version skill is a step-by-step runbook that lets an AI agent prepare the next Prisma release for a maintainer. It bumps the version in the root package.json and every workspace package, refreshes the lockfile, checks the diff, and opens a pull request titled 'chore(release): bump to <next-version>'. After this guide you will know what the skill does, how to install it, how to ask for it in plain language, and what it needs before you run it.

Publish Next Prisma npm Versionprisma/orm · Apache-2.0

Quick start

  1. 1Download and unzip the skill. Download the ZIP from this page and unzip it into ~/.claude/skills/ for a personal install or into .claude/skills/ inside the project. You can also upload the ZIP under Settings → Capabilities → Skills in the Claude apps.
  2. 2Confirm your requirements. Check that git can reach the prisma/orm origin remote, Node.js and pnpm are installed, and you have write access to push branches and open PRs on GitHub.
  3. 3Make the request. Ask the agent in plain language to cut the next release or prepare a publish PR for prisma/orm.
  4. 4Let the agent fetch and create a worktree. The agent runs git fetch origin main and creates a fresh release worktree from origin/main so your current branch is not disturbed.
  5. 5Run the bump and lockfile refresh. The agent runs pnpm bump-version and then pnpm install --lockfile-only, and confirms the version matches what it computed earlier.
  6. 6Review the diff and PR. Check that only version fields, workspace specifiers and the expected stamp files changed, then review the opened pull request.
  7. 7Merge as a human decision. Merging the PR is the step that triggers the Publish to npm workflow, so merge only after you are satisfied with the diff and release notes.

What the skill makes the agent do

An agent skill is a folder containing a SKILL.md file with instructions that an AI agent reads and follows when a request matches the skill's description. This one is written for Prisma maintainers who have permission to push branches and open pull requests in the prisma/orm repository.

The skill works in a fresh git worktree created from origin/main, so your current feature branch is left untouched. It works out the next version using the repository's release rules, writes it to every package, refreshes pnpm-lock.yaml, and checks that the changes are limited to version fields and workspace specifiers. It also prepares the matching prisma/web docs-site pull request from the same release notes.

  • Fetches origin/main and computes the next release version
  • Creates a release branch and worktree named after that version
  • Runs pnpm bump-version and confirms the result matches
  • Refreshes the lockfile and checks the diff for unexpected changes
  • Opens the release pull request for a human to review
git fetch origin main

Install the publish-npm-version skill

Download the ZIP for the skill from this page. You can install it for yourself across all projects, or for a single project.

For a personal install, unzip the download into ~/.claude/skills/. For a project-only install, unzip it into the .claude/skills/ folder inside the project. You can also upload the ZIP in the Claude apps under Settings → Capabilities → Skills.

After installing, confirm the folder contains SKILL.md. The skill is invoked locally by the maintainer and does not run as a GitHub Action.

  • Personal: ~/.claude/skills/
  • Project: .claude/skills/ inside the repository
  • Claude apps: Settings → Capabilities → Skills, then upload the ZIP

Check the requirements before you start

The skill assumes you are already a Prisma maintainer working inside the repository. It cannot grant you access, and it depends on repository scripts and workflows that must already exist.

Make sure you have the following before you ask the agent to start.

  • git with access to the prisma/orm origin remote, and git fetch origin main succeeding
  • Node.js and pnpm
  • The repository scripts scripts/determine-version-utils.ts and scripts/set-version.ts
  • Write access to push branches and open PRs on GitHub
  • The draft-release-notes skill, which the release process uses for release notes

Trigger the skill with natural requests

You do not need a special command. Describe what you want in plain language and the agent will match your request to the skill's description. The skill is designed for requests about cutting a release or preparing a release pull request.

Phrases that match the skill include asking to cut the next RC, cut the next release, bump to the next version, open a release PR, or prepare a publish PR. Mention the repository and the goal so the agent starts from the right checkout.

  • 'Cut the next RC for prisma/orm and open the release PR.'
  • 'Bump to the next version and open a release PR.'
  • 'Prepare a publish PR for the next release.'

What happens during a run

The agent first runs git fetch origin main and works out the next version from the current origin/main version. It then creates a fresh worktree and runs pnpm bump-version inside it. If the worktree has no node_modules, the agent is expected to run pnpm install --frozen-lockfile --ignore-scripts first.

After the bump, the agent runs pnpm install --lockfile-only so the lockfile matches the new workspace specifiers. Without that step, CI fails on the release PR with ERR_PNPM_OUTDATED_LOCKFILE. The agent then checks that only expected files changed and prepares the release notes.

  • Package.json diffs should contain only version changes and internal workspace specifier changes
  • pnpm-lock.yaml should change only in workspace specifiers
  • Any mismatch between the computed versions stops the process for review
pnpm install --lockfile-only

Understand publishing and the human merge step

Opening the pull request does not publish anything. When a maintainer merges the PR, the existing Publish to npm workflow runs automatically and ships the new version to npm under the dist-tag implied by its shape. RC releases get a pre-release GitHub Release, and a matching GitHub Release is created.

Merging stays a human decision. The skill is a preparation tool, and it does not handle emergency patch releases.

  • Stable releases ship under the latest dist-tag
  • RC releases get a pre-release GitHub Release
  • The skill does not handle emergency patches

Safety notes: scripts and network access

This skill runs scripts and uses the network. It runs repository scripts, fetches from the origin remote, and pushes a branch and opens a pull request on GitHub. Those actions are real changes to the repository, so review what the agent does before you merge anything.

Because a wrong release is hard to undo on npm, read the release PR diff carefully and do not merge until the changes match what you expect. The skill stops and reports the problem if a precondition is not met instead of trying to fix it silently.

  • Review the diff before merging the PR
  • Do not run the skill with credentials you do not control
  • Stop and investigate if the agent reports a version mismatch

What people use it for

  • Cutting the next RC on the Prisma release line with a reviewable pull request
  • Opening a stable release PR once a maintainer decides the release is ready
  • Preparing a matching prisma/web docs-site PR from the same release notes
  • Checking a version bump diff for unexpected changes before anyone reviews it

Frequently asked questions

Is the publish-npm-version skill free to use?

The skill is listed under the Apache-2.0 licence. The licence terms are in the repository, and you should check them before reuse. Using the skill still requires Prisma maintainer access to push branches and open pull requests.

How do I install the publish-npm-version skill?

Download the ZIP from this page and unzip it into ~/.claude/skills/ for a personal install, or into .claude/skills/ inside a project. You can also upload the ZIP in the Claude apps under Settings → Capabilities → Skills.

What does the skill need to run?

It needs git with access to the prisma/orm origin remote, Node.js and pnpm, the repository scripts scripts/determine-version-utils.ts and scripts/set-version.ts, and write access to push branches and open PRs on GitHub. It also relies on the draft-release-notes skill for release notes.

Can someone outside the Prisma team use this skill?

Not usefully. The skill needs repository push access and assumes internal scripts and workflows exist. It is written for maintainers who run it locally.

Does the skill publish to npm by itself?

No. It opens a pull request. Merging that PR is the step that triggers the existing Publish to npm workflow, and merging stays a human decision.

Can the skill handle an emergency patch release?

No. The skill explicitly does not handle patches. Emergency patch releases follow a separate path described in the versioning documentation, and a wrong release is hard to undo on npm.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

Use this skill if you are a Prisma maintainer with push and PR rights who needs to cut the next RC or stable release and wants the version bump and diff checks done consistently. Pick something else if you are not on the maintainer team, or if you need an emergency patch release, since this skill does not handle patches.

Download the skill