Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →remotion-dev/update-remotion-rust-ffmpeg
Update Remotion's ffmpeg-next Git revision to a published rust-ffmpeg commit, refresh Cargo.lock, rebuild all supported compositor binaries, validate the monorepo, and open a draft pull request.
Passed 13 of 19 test cases with the skill, and 4 of 19 without it.
and 16 more in the full report
12 fixed5 passed either way8 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are committing our staged compositor updates. A developer suggests using `chore(compositor): bump rust-ffmpeg to SHA`. What exact commit title is required?
| Checked | Without skill | With skill |
|---|---|---|
| Uses `@remotion/compositor`: Update rust-ffmpeg and rebuild binaries as the commit and PR title. | Missed | Passed |
The instructions your model reads when the skill loads.
Require the full published rust-ffmpeg commit SHA from $update-rust-ffmpeg-sys.
Read ../pr/SKILL.md and ../pr-name/SKILL.md before committing or opening the pull request.
Run from the dedicated Remotion worktree on codex/update-rust-ffmpeg. Never perform this work in the primary /Users/jonathanburger/remotion checkout.
Fetch origin. If the branch has no release commits yet, fast-forward it to origin/main. Do not rebase, reset, or overwrite unrelated work.
Allow this skill's own tracked .agents/skills/update-remotion-rust-ffmpeg files to exist unchanged. Stop on any pre-existing change that is not explicitly part of the requested pull request.
Verify that the supplied full SHA is reachable from remotion-dev/rust-ffmpeg's main branch. Read that commit's Cargo.toml and record the exact ffmpeg-sys-next revision for later lockfile verification.
Change only the ffmpeg-next.rev value in packages/compositor/Cargo.toml to the supplied full SHA. From packages/compositor, run:
cargo update -p ffmpeg-next
Verify in Cargo.lock that:
ffmpeg-next resolves to the supplied rust-ffmpeg SHA;ffmpeg-sys-next resolves to the recorded rust-ffmpeg-sys SHA.Install workspace dependencies without changing the lockfile:
bun install --frozen-lockfile
Install cross-compilation toolchains if packages/compositor/toolchains is absent:
cd packages/compositor
bun install-toolchain.ts
test cases passed, vs 4 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.