agentleFS
Sign inStart free
harvatechsharvatechs/inthon/.agents/skills/remotion-upgrade/SKILL.md

remotion-upgrade

Skill2 starsChanged 4 months agoApache-2.0View on GitHub

Upgrade Remotion, its related packages, compatible Mediabunny packages, and installed Remotion Agent Skills. Use when asked to upgrade or update a Remotion project.

23 other projects use a version of this, 20 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use remotion-license.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • mia-cxSkill

    remotion-license

    Find Remotion license information, FAQs, terms, and where to buy a license.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 1 is common, 2 are distinctive, and 1 is very specific to this project.

  • 1

    Common

    Most of the 20 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If @remotion/cli is not available, upgrade manually:

    line 17
  2. Distinctive:

    Read the current Mediabunny compatibility page and determine the Mediabunny version compatible with the target Remotion version.

    line 20
  3. Common:

    Run the project's package manager to update its lockfile.

    line 21
  4. Distinctive:

    Update the installed Remotion skills:

    line 22

“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Upgrade Remotion

  1. Inspect the project manifests and lockfile to identify the package manager and workspaces. Preserve unrelated changes.

  2. Determine whether @remotion/cli is locally available. If it is, run:

    npx remotion upgrade

    Skip the manual package upgrade below.

  3. If @remotion/cli is not available, upgrade manually:
    • Get the latest stable Remotion version with npm view remotion version.
    • Find every installed remotion and @remotion/* dependency across the project and upgrade them all to that exact version. Preserve their dependency sections and the project's workspace or catalog conventions.
    • Read the current Mediabunny compatibility page and determine the Mediabunny version compatible with the target Remotion version. Upgrade every installed mediabunny and @mediabunny/* package to the documented compatible version.
    • Run the project's package manager to update its lockfile.

  4. Update the installed Remotion skills:

    npx remotion skills update
  5. Review the manifest and lockfile diff. Ensure all Remotion packages use one version and all installed Mediabunny packages use the compatible version. If the CLI is available, run npx remotion versions as an additional check.

The Remotion releases contain the changelog and may be useful for summarizing relevant changes after the upgrade.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free