Tanstack Router Migration
CheckedAutomates TanStack Router v1 to v2 migration, minimizing disruption and ensuring seamless application updates.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add redpanda-data/console --skill tanstack-router-migration -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
redpanda-data
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.
Automated safety checks
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 redpanda-data/console at 0d2c900a21.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 0d2c900a21
- Scanned
- 5 files, 2,289 lines
About this skill
What it does
This skill automates the migration of React applications from React Router to Tanstack Router, facilitating a smoother transition and minimizing disruption during application updates. It provides a structured process for both incremental and complete migrations, leveraging file-based routing within your project's src/routes directory. The tool generates code and configuration files to streamline this process while maintaining type safety and ensuring compatibility.
When to use it
- You are upgrading an existing React application that currently uses React Router.
- You want to adopt Tanstack Router’s file-based routing approach for improved organization and maintainability.
- You need a structured guide to migrate your application, including considerations for route guards and custom components.
- Your project utilizes TypeScript and you require type safety during the migration process.
Key capabilities
- Automated generation of router configuration files (
routeTree.gen.ts). - Support for incremental or complete migrations.
- File-based routing within a designated
src/routesdirectory. - TypeScript integration with the use of the
fromparameter in hooks and Zod schema validation. - Configuration plugins for build tools like Rspack, Rsbuild, and Vite.
Example prompts
- "Migrate my React Router v6 application to Tanstack Router."
- "Generate a router configuration file for my project using the
@tanstack/router-pluginwith Rspack." - "Show me how to configure linting rules specifically for files within my
src/routesdirectory."
Tips & gotchas
- Build Tool Configuration is Crucial: Properly configuring your build tool plugin (Rspack, Rsbuild or Vite) before creating routes is essential. Refer to the provided documentation (
references/build-configuration.md) for detailed instructions. - Avoid Manual Editing: Do not directly edit the auto-generated
routeTree.gen.tsfile, as changes will be overwritten during subsequent migrations. - Type Safety Matters: Always use the
fromparameter in hooks to ensure type safety during the migration process.