mcpbeat

Bumping Biome

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).

389 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
418
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 bumping-biome

The instruction itself

3 sections, as written by the author

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.
  • Rename all biome.json files to biome.jsonc and replace the old package version number in $schema with the newly installed package version number from the previous step.
  • 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.

How to use it

Copy the folder

Take prisma/bumping-biome 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.