Skip to content
TrustedSkillsbeta
Back to all skills

Rsbuild V2 Upgrade

Checked
rstackjs·vlatest·other·MIT

This skill upgrades your Rsbuild V2 project to the latest version, ensuring optimal performance and access to new features for faster builds.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add rstackjs/agent-skills --skill rsbuild-v2-upgrade -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

rstackjs

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned rstackjs/agent-skills at 1ccaad5ecc.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
1ccaad5ecc
Manifest
skills/rsbuild-v2-upgrade/SKILL.md
Scanned
1 file, 35 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

rsbuild-v2-upgrade

What it does

This skill automates the migration of existing Rsbuild projects from version 1 to version 2. It handles complex configuration transformations and updates dependencies to ensure compatibility with the new architecture.

When to use it

  • You are maintaining a legacy Rsbuild v1 application that requires security patches or performance improvements available in v2.
  • Your team needs to adopt the latest build optimizations and plugin ecosystem introduced in the Rsbuild v2 release cycle.
  • You want to streamline the upgrade process by avoiding manual, error-prone configuration rewrites.

Key capabilities

  • Automatically detects and migrates project configurations from Rsbuild v1 syntax to v2 standards.
  • Updates package dependencies to align with the new version requirements.
  • Preserves custom build logic while adapting it to the updated framework structure.

Example prompts

  • "Migrate my current Rsbuild v1 project to v2 using the automated upgrade tool."
  • "Run the rsbuild-v2-upgrade skill and show me the changes made to my config file."
  • "Upgrade my build system to Rsbuild v2 and verify all plugins are compatible."

Tips & gotchas

Ensure your project is backed up before running the migration, as automated tools may not catch every edge case in custom configurations. Review the generated diff carefully to confirm that business logic remains intact after the version switch.