Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →remotion-dev/pr
Open a pull request for the current feature
Passed 7 of 13 test cases with the skill, and 3 of 13 without it.
and 9 more in the full report
8 fixed3 passed either way9 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/2/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
The Vercel bot posted a comment on my GitHub PR containing two deployment rows: one for `remotion` and one for `bugs`. Which row's preview link should be used when appending page paths?
| Checked | Without skill | With skill |
|---|---|---|
| Selects the preview URL from the `remotion` project row. | Missed | Passed |
| Ignores deployment links from the `bugs` project row. | Missed | Passed |
The instructions your model reads when the skill loads.
Ensure we are not on the main branch, make a branch if necessary.
Check whether a PR already exists for the current branch with gh pr status or gh pr view. If one exists, update it with local changes.
Keep new agent-authored tests, including new test cases in existing files, out of the PR unless the user explicitly requested them. Updates to existing tests, fixtures, and snapshots are allowed when needed for the change. Review the diff and preserve pre-existing user changes.
If the changes add a Remotion Element, read the Element contribution guide before continuing.
Run Oxfmt on the files or package directories affected by the current change. Pass their actual paths; do not assume that the repository root has a src directory. Include relevant root-level files, and do not format unrelated packages or the whole repository.
For example:
bunx oxfmt <changed-file-or-package-directory>... --write
If none of the changed files are supported by Oxfmt, skip this step. Inspect any formatter changes before committing.
Then run
bun run build
bun run stylecheck
to ensure we compile and CI linting/formatting passes.
Commit the changes once. The title of the PR must be according to the pr-name skill.
Push the changes to the remote branch once, using git push -u origin HEAD.
Never force push, unless users asks for it.
Use the gh CLI to create a pull request and use the same format as above for the title.
When creating the PR, do not pass the PR body inline through a shell command (for example, avoid --body "..." or heredocs in bash). Instead:
/tmp/remotion-pr-body.md, or a unique file created under /tmp).
Closes #1234 or Closes https://github.com/owner/repo/issues/1234. Preserve the issue number or URL from the user's original request if they provided one.gh pr create --title "<title>" --body-file <path-to-temp-md-file>.test cases passed, vs 3 / 13 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.