Agent skill · software engineering · remotion-dev
pr
Open a pull request for the current feature
Why this skill is useful
Adds a detailed executable script for automating the pull request process with specific commands and checks that enhance the AI's capabilities.
What it needs
Requires bun, gh, vercel installed locally. Requires github account access. About 2k tokens when loaded. Last updated 2026-08-06. 55,698 stars on the source repository.
What this skill does
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: If none of the changed files are supported by Oxfmt, skip this step. Inspect any formatter changes before committing. Then run 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: 1. Write the PR body to a temporary Markdown file in the system temp directory (for example /tmp/remotion-pr-body.md, or a unique file created under /tmp). If the current work was started from, fixes, or is otherwise tied to a GitHub issue, include a closing keyword in the PR body such as 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. 2. Create the PR with gh pr create --title "<title>" --body-file <path-to-temp-md-file>. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills remotion-dev/pr