Install any skill in seconds. Free to start, no credit card required.
Get Started Free →remotion-dev/update-version
Update `AvailableFrom` in a PR to the next Remotion patch version (`main` + `0.0.1`).
Passed 16 of 19 test cases with the skill, and 9 of 19 without it.
and 8 more in the full report
9 fixed9 passed either way3 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am ready to check the canonical version from main in the Remotion repository before updating doc tags. I have local main checked out. What exact git fetch command should I run before showing the remote file content?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies running git fetch origin main --quiet | Missed | Passed |
The instructions your model reads when the skill loads.
Use this when a PR contains docs changes with <AvailableFrom v="..."> and the value should reflect the next release version.
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).
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.
test cases passed, vs 9 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.