bumping-biome
$
npx mdskill add prisma/prisma-next/bumping-biomeUpdates Biome packages and aligns configuration files using pnpm
- Solves the need to update Biome packages to the latest or specified version
- Uses pnpm for version updates and file alignment across the repository
- Relies on provided version or defaults to latest if unspecified
- Reports issues and offers fixes to ensure consistent Biome configuration
SKILL.md
.github/skills/bumping-biomeView on GitHub ↗
--- 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.
More from prisma/prisma-next
- adr-review>-
- ast-visitor-pattern>-
- contrib-prOpen a high-quality external contributor PR against prisma-next. Use when the user is an outside contributor (not a Prisma maintainer) and wants to submit a change as a pull request from a fork. Encodes the contribution flow from CONTRIBUTING.md so the resulting PR passes review on the first round.
- drive-agent-personasLibrary of agent personas — named bias-frames that other skills load to shift execution-time defaults. Skills name a persona by ID (e.g. "Adopt the architect persona"), and this skill resolves that ID to the persona doc that frames the executor for the rest of the task. Use when authoring a new skill that needs a particular reviewer/implementer/orchestrator stance, or when an existing skill instructs you to adopt a named persona.
- drive-create-plan>
- drive-create-project>
- drive-create-spec>
- drive-discussionDrops the agent into a structured Q&A mode that iterates with the user toward a complete understanding of a topic, then documents the outcome (project spec, plan, decision record, or whatever shape fits). The agent adopts one or more personas from the `drive-agent-personas` library — named explicitly by the user, or inferred from conversation context and announced. Typical use is design work at the start of a task, or mid-implementation when a load-bearing assumption has been falsified. Use ONLY when the user explicitly invokes this skill (e.g. "discussion mode", "pressure-test this", "let's design this", "design mode", "tech design mode", "product mode", "pm mode", "challenge my idea"). Never auto-invoke.
- drive-orchestrate-plan>
- drive-pr-descriptionGenerates PR descriptions by analyzing git diffs between the current branch and the default branch. Use when the user requests a PR description, pull request summary, or commit message for a squash merge.