Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →remotion-dev/update-from-upstream-main
Update the current Remotion branch with the latest canonical main branch.
Passed 5 of 13 test cases with the skill, and 6 of 13 without it.
and 2 more in the full report
4 fixed5 passed either way8 still failing5 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
I checked my remotes using git remote -v, and origin points to my-fork/remotion while fork-remote points to another developer's repo. Neither remote points to remotion-dev/remotion. Should you automatically add a new remote or ask the user first?
| Checked | Without skill | With skill |
|---|---|---|
| Stops execution when no remote points to remotion-dev/remotion | Passed | Passed |
| Prompts the user for instruction before adding or altering remotes | Missed | Passed |
The instructions your model reads when the skill loads.
Update from the canonical remotion-dev/remotion repository while preserving local work and published branch history.
Inspect the repository before changing it:
git status --short --branch
git branch --show-current
git remote -v
Stop and report the state if an operation such as a merge or rebase is already in progress. A detached checkout is supported and must not prevent the update.
If the working tree contains staged, unstaged, or untracked changes, stash them automatically and continue:
git stash push --include-untracked --message "update-from-upstream-main: preserve local changes"
git rev-parse stash@{0}
Record the created stash's commit ID so the same entry can be restored later. Do not treat uncommitted changes as a reason to stop. Do not include ignored files unless the user explicitly asks.
Select the canonical remote whose URL points to remotion-dev/remotion. Prefer upstream when it exists; otherwise use origin. If neither remote points to the canonical repository, stop and ask before adding or changing a remote.
Fetch the latest main branch without changing the working tree:
git fetch <canonical-remote> main
Update the checked-out branch:
On main, require a fast-forward:
git merge --ff-only <canonical-remote>/main
test cases passed, vs 6 / 13 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.