mcpbeat

Update Version

remotion-dev/update-version

Update `AvailableFrom` in a PR to the next Remotion patch version (`main` + `0.0.1`).

230 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
55471
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/remotion-dev/remotion --skill update-version

The instruction itself

as written by the author

Use this when a PR contains docs changes with <AvailableFrom v="..."> and the value should reflect the next release version.

  • Get the canonical version from main:
git fetch origin main --quiet
git --no-pager show origin/main:packages/core/src/version.ts

Read VERSION from that file (for example: 4.0.468), then compute the next patch version by incrementing the patch number by 1 (4.0.469).

  • Find AvailableFrom entries changed in the current PR:
git --no-pager diff origin/main...HEAD -- packages/docs | rg 'AvailableFrom v="'
  • Update only AvailableFrom values touched by this PR so they match the computed next patch version from step 1.
  • Do not change unrelated AvailableFrom values outside the PR diff.
  • Commit and push the update.

How to use it

Copy the folder

Take remotion-dev/update-version from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.