rsbuild-v2-upgrade — Claude Code skill: migrate Rsbuild 1.x to v2
Walks a Rsbuild 1.x project through the v2 migration: dependencies, config, breaking options. Useful when a major bump would otherwise eat an evening.
npx skills add rstackjs/agent-skills --skill rsbuild-v2-upgrade -a claude-codeWhat rsbuild-v2-upgrade does
The skill inspects your setup first. It reads package.json to find the Rsbuild and plugin packages in use, then locates the config file — usually rsbuild.config.(ts|js|mjs|cjs). From there it compares the project against the official v1 → v2 guide and lists the breaking changes that actually apply: removed or renamed options, changed defaults, plugin API shifts.
Dependency bumps run on two tracks. @rsbuild/core goes to v2, and the Rsbuild plugins move to their latest majors with npx taze major --include /rsbuild/ -w -r. Then come the config and code edits: drop settings v2 no longer supports, align the rest with the new options. Validation closes the loop — build, dev command, tests or type checks, with the new version's warnings worked through.
The official guide is the source of truth here, not the model's memory, so the skill opens it before planning anything. If your project uses a plugin the guide doesn't cover, you'll have to check that behaviour yourself.
What it helps with
- bump @rsbuild/core to v2 without missing breaking changes
- find config options that v2 removed or renamed
- update Rsbuild plugins to their latest majors in one command
- work through warnings and errors after the version switch
- re-run build, dev and tests once the migration lands
Example prompts for the agent
- Upgrade this project from Rsbuild 1.x to v2 and show what breaks in the config
- Go through the migration guide and list the changes for my rsbuild.config.ts
- Bump @rsbuild/core to v2 and verify the build and tests
How to install rsbuild-v2-upgrade
1Skills CLI (Vercel)
npx skills add rstackjs/agent-skills --skill rsbuild-v2-upgrade -a claude-code2Manually: put the files in place
~/.claude/skills/rsbuild-v2-upgrade/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/rsbuild-v2-upgrade/
1Skills CLI (Vercel)
npx skills add rstackjs/agent-skills --skill rsbuild-v2-upgrade -a codex2Manually: put the files in place
.agents/skills/rsbuild-v2-upgrade/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add rstackjs/agent-skills --skill rsbuild-v2-upgrade -a cursor2Manually: put the files in place
.cursor/skills/rsbuild-v2-upgrade/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install rstackjs/agent-skills rsbuild-v2-upgrade2Manually: put the files in place
.github/skills/rsbuild-v2-upgrade/SKILL.md1Skills CLI (Vercel)
npx skills add rstackjs/agent-skills --skill rsbuild-v2-upgrade -a gemini-cli2Platform CLI
gemini skills install https://github.com/rstackjs/agent-skills --path skills/rsbuild-v2-upgradeManually: put the files in place
.devin/skills/rsbuild-v2-upgrade/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add rstackjs/agent-skills --skill rsbuild-v2-upgrade -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about rsbuild-v2-upgrade
How do I install rsbuild-v2-upgrade in Claude?
Run npx skills add rstackjs/agent-skills --skill rsbuild-v2-upgrade -a claude-code. The skill lands at ~/.claude/skills/rsbuild-v2-upgrade/SKILL.md.
What does rsbuild-v2-upgrade do?
It drives the Rsbuild 1.x to v2 migration: reads package.json and the config, checks the official guide, updates dependencies and settings, then validates the build and tests.
How is this different from just asking a model about Rsbuild v2?
It treats the official v1 → v2 guide as the source of truth and starts from your project's current config instead of answering from general recall about the library.
Source text
SKILL.md · MIT
---
name: rsbuild-v2-upgrade
description: Use when upgrading a Rsbuild 1.x project to v2, including dependency and configuration updates.
---
# Rsbuild v1 to v2 upgrade
## Workflow
1. **Confirm current setup**
- Read `package.json` to identify Rsbuild and plugin packages in use.
- Locate the Rsbuild config file (commonly `rsbuild.config.(ts|js|mjs|cjs)`).
2. **Open the official upgrade guide**
- Use the v1 → v2 guide as the source of truth:
- https://rsbuild.rs/guide/upgrade/v1-to-v2
3. **Plan the upgrade path**
- Compare the current project config with the migration guide.
- List breaking changes that apply to the project’s current config and plugins.
- Note any removed or renamed options, defaults, or plugin APIs.
4. **Update dependencies**
- Bump `@rsbuild/core` to v2
- Bump Rsbuild plugins to latest versions via `npx taze major --include /rsbuild/ -w -r`
5. **Apply config and code changes**
- Update the Rsbuild config to match v2 options and defaults.
- Remove deprecated or unsupported settings.
6. **Validate**
- Run the build and dev commands.
- Run project tests or type checks.
- Fix any warnings or errors surfaced by the new version.
© rstackjs · MIT · rstackjs/agent-skills
