Update Version
Bump `<AvailableFrom v="...">` in Remotion docs PRs to the next patch version derived from `main`'s `VERSION` in `packages/core/src/version.ts`.
Install
npx skills add https://github.com/remotion-dev/remotion --skill update-versionWhat is this skill?
- Reads canonical `VERSION` from `origin/main:packages/core/src/version.ts` after `git fetch origin main`
- Computes next patch by incrementing patch segment by 1 (example 4.0.468 → 4.0.469)
- Scopes changes to `AvailableFrom` lines touched in PR diff via `git diff origin/main...HEAD -- packages/docs`
- Does not alter unrelated `AvailableFrom` values outside the PR
- Ends with commit and push of version alignment
Adoption & trust: 81 installs on skills.sh; 49.4k GitHub stars.
Recommended Skills
Release Skillsjimliu/baoyu-skills
Changelog Automationwshobson/agents
Msstore Cligithub/awesome-copilot
Changelog Generatorcomposiohq/awesome-claude-skills
Shopify App Store Reviewshopify/shopify-ai-toolkit
Shipping And Launchaddyosmani/agent-skills
Journey fit
Primary fit
Ship → launch fits doc version gates tied to an upcoming Remotion patch release, not feature implementation. Launch subphase covers release-prep artifacts—docs must advertise the correct availability version before users see the feature.
SKILL.md
READMESKILL.md - Update Version
Use this when a PR contains docs changes with `<AvailableFrom v="...">` and the value should reflect the next release version. 1. Get the canonical version from `main`: ```bash 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`). 2. Find `AvailableFrom` entries changed in the current PR: ```bash git --no-pager diff origin/main...HEAD -- packages/docs | rg 'AvailableFrom v="' ``` 3. Update only `AvailableFrom` values touched by this PR so they match the computed next patch version from step 1. 4. Do not change unrelated `AvailableFrom` values outside the PR diff. 5. Commit and push the update.