How do I install the Bumping Biome skill?

Run npx skillmds add prisma-orm/bumping-biome in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Bumping Biome safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Bumping Biome?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Bumping Biome free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Bumping Biome?

prisma (@prisma-orm) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Bumping Biome by prisma-orm — Agent Skill

Name: Bumping Biome
Rating: 4.2 (5 reviews)
Author: prisma

Bumping Biome

Bumps `biome` package versions (e.g. `@biomejs/biome`) using `pnpm`, aligns `biome.jsonc` files with the new version/s across the repository and runs biome-related checks. Use when required to update `biome` to a newer version - explicitly or implicitly (e.g. after running `pnpm up`, `pnpm update`, `pnpm upgrade` without specific package names).

prisma 461c859 1.6 KB Updated Sep 9, 2026

File contents

Bumping Biome Skill

Instructions

Run pnpm up -D -w -r @biomejs/biome@<version> - replace <version> with a specific package version provided in the session, otherwise fallback to latest.
If any biome.json files remain, rename them to biome.jsonc. Then replace the old package version number in $schema with the newly installed package version number from the previous step, in every biome.jsonc.
Run pnpm -w lint:fix. Report any issues/regressions briefly.
If there are remaining unsafe fixes following the previous step, offer to run pnpm -w lint:fix:unsafe to attempt to fix some of the issues/regressions.
If the offer in the previous step is agreed, run the appropriate command, and report any remaining issues/regressions briefly.
If there are remaining issues/regressions after the previous step, try and come up with your own suggestions for fixing them and present the plan.

Don't Do

Don't scan for biome versions. If the session doesn't include a specific package version number, use latest.
Don't read the root package.json or lockfiles looking for the current biome version/s. We'll see the change in version numbers in Git anyway.

Frequently asked questions