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

Jump to install

Repository: prisma/prisma-next
Last source activity: May 17, 2026 at 12:41
Detected SKILL.md language: English
Stars: 417
Forks: 17

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/prisma/prisma-next --skill bumping-biome

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

name: bumping-biome
description: 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).

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

View on GitHub

Back to search Back to installation

prisma-next-extension-upgrade

Upgrade Prisma Next in your extension. Bumps every `@prisma-next/*` dependency to the requested target (or npm `latest`), runs the per-transition upgrade instructions for the extension SPI (middleware lifecycle, codec / migration-tools / framework-components churn, seed-migration on-disk shape), verifies the pins are correctly exact via `prisma-next-check-pins`, runs the extension's own typecheck and tests, and commits each minor step on its own. Use when the user asks to "upgrade Prisma Next" in an extension package, or to update an extension's `@prisma-next/*` deps to a new minor.

2026-07-27

prisma-next-contract

Edit the Prisma Next data contract — add models, fields, relations, indexes, enums, value objects (composite types), type aliases, namespaces (Postgres schemas), cross-contract foreign keys (cross-space FK), polymorphic types (`@@discriminator` / `@@base`), use extension namespaces (`pgvector.Vector(...)`, `cipherstash.EncryptedString(...)`), wire `prisma-next.config.ts` with `defineConfig` from the `@prisma-next/<target>/config` façade, and run `prisma-next contract emit`. Use for schema, models, fields, attributes, soft delete, paranoid, scopes, validations, callbacks, prisma schema, PSL, contract.prisma, contract.ts, contract.json, contract.d.ts, `@prisma-next/postgres/config`, `@prisma-next/postgres/contract-builder`, `@prisma-next/postgres/control`, `@prisma-next/mongo/config`, `@prisma-next/mongo/contract-builder`, `extensions:`, pgvector, cipherstash, postgis, paradedb, supabase, `@prisma-next/extension-supabase`, `@@control`, control policy, managed, tolerated, external, observed.

2026-07-27

prisma-next-upgrade

Upgrade Prisma Next in your app. Bumps every `@prisma-next/*` dependency from the version pinned in the lockfile to the requested target (or npm `latest`), applies any required code-translation steps from the per-transition upgrade instructions, validates with the project's own typecheck + tests, and commits each minor step on its own. Use when the user asks to "upgrade Prisma Next", "bump Prisma Next", "move to Prisma Next X.Y", or asks an agent to deal with an `@prisma-next/*` minor bump in their app.

2026-07-27

View all from this repository

bumping-biome

Source facts

Install options

Review the source files

More from this repository

More from this repository