A five-step upgrade routine for Remotion projects. The agent identifies the package manager and workspaces, then runs npx remotion upgrade when the CLI is present. Without the CLI it finds the latest stable version, moves every remotion and @remotion/* dependency to that exact version, and aligns zod, mediabunny and similar packages with the versions Studio lists.
It finishes by updating the installed Remotion skills and reviewing the manifest and lockfile diff.
What You Get
- A first-choice path using npx remotion upgrade when @remotion/cli is installed
- A manual path: read the latest version with npm view, upgrade all remotion and @remotion/* packages to the same exact version, and refresh the lockfile
- A rule to read @remotion/studio dependencies for the target version and align zod, mediabunny, @huggingface/transformers and @mediabunny packages
- A command to update all thirteen Remotion skills
- A final check of the diff and of npx remotion versions
Common Use Cases
- Moving a project to the latest Remotion release
- Fixing a version mismatch between Remotion packages
- Bringing Mediabunny in line with what Studio expects
- Refreshing installed Remotion agent skills after a release
What Makes It Unique
It treats the upgrade as one version across all Remotion packages and also aligns the auxiliary packages Studio depends on, which are easy to miss. It respects workspace and catalog conventions and keeps unrelated changes, and it ends with a check for mixed versions.
Under The Hood
The skill is instructions only, with no scripts. It tells the agent to read package manifests and lockfiles, run npx remotion upgrade, or use npm view to query the npm registry, edit dependency versions, run the project’s package manager to update the lockfile, and run npx skills update for the Remotion skills. It changes files in the project and installs packages from the network.