AugmentClaude

Biome Version Bumper

Update Biome package versions and align configuration files across your repository.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/bumping-biome-prisma/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

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

What this skill does

Bumping Biome Skill

Instructions

  1. Run pnpm up -D -w -r @biomejs/biome@<version> - replace <version> with a specific package version provided in the session, otherwise fallback to latest.

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

  3. Run pnpm -w lint:fix. Report any issues/regressions briefly.

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

  5. If the offer in the previous step is agreed, run the appropriate command, and report any remaining issues/regressions briefly.

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

  1. Don't scan for biome versions. If the session doesn't include a specific package version number, use latest.

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

Related skills