OpenParable
Skip to content
← Back to skills

PR

Development
pr

PR is an Agent Skill for development published in the remotion-dev/remotion repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Open a pull request for the current feature

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/remotion-dev/remotion/blob/HEAD/.agents/skills/pr/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/pr, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

This skill is only for opening the initial pull request from finished local work.

If a PR already exists for the current branch, stop: do not format, commit, push, amend, or rebase unless the user explicitly asks for that Git action. Leave follow-up changes uncommitted by default.

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 it exists, report it and stop.

For all packages affected, run Oxfmt to format the code:

bunx oxfmt src --write

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. Do not use git push --force, git push -f, or git push --force-with-lease. If a normal push is rejected, stop and report the rejection to the user instead of rewriting remote history.

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>.

Example:

gh pr create --title '`@remotion/package`: Add feature' --body-file /tmp/remotion-pr-body.md