PluginBench
Skill
Official
Review
Audit score 70

make-pr

remotion-dev/remotion

Create a formatted pull request following Remotion's conventions

What is make-pr?

Automates the pull request workflow for Remotion contributions. Ensures code is formatted, committed with proper naming, and pushed to a remote branch before opening the PR via GitHub CLI.

  • Verifies you're not on the main branch and creates a feature branch if needed
  • Runs Oxfmt to format code across all affected packages
  • Commits changes with a properly formatted title
  • Pushes changes to the remote branch
  • Opens a pull request using the GitHub CLI with standardized naming

How to install make-pr

npx skills add https://github.com/remotion-dev/remotion --skill make-pr
Prerequisites
  • GitHub CLI (gh) installed and authenticated
  • Bun package manager installed
  • Access to Remotion repository with push permissions
Claude Code
Cursor
Windsurf
Cline

How to use make-pr

  1. 1.Create or switch to your feature branch (the skill will create one if needed)
  2. 2.Make your code changes in the affected packages
  3. 3.Run the skill to format code with Oxfmt, commit, push, and open the PR
  4. 4.The PR will be created with a title matching the pr-name skill format

Use cases

Good for
  • Streamline contribution workflow when working on Remotion features
  • Ensure consistent code formatting before submitting PRs
  • Automate repetitive PR creation steps for multiple contributions
  • Maintain naming conventions across all pull requests in the Remotion project
Who it's for
  • Remotion contributors
  • Open-source developers working on Remotion
  • Team members following Remotion's PR conventions

make-pr FAQ

What if I'm already on main branch?

The skill checks for this and will create a new feature branch before proceeding.

How is the PR title formatted?

The PR title follows the format defined in the pr-name skill; refer to that skill's documentation for naming conventions.

Do I need to manually push my changes?

No, the skill handles pushing to the remote branch automatically before creating the PR.

What code formatter does this use?

It uses Oxfmt, which is run on the src directory of all affected packages.

Full instructions (SKILL.md)

Source of truth, from remotion-dev/remotion.


name: make-pr description: Open a pull request for the current feature

Ensure we are not on the main branch, make a branch if necessary.
For all packages affected, run Oxfmt to format the code:

bunx oxfmt src --write

Commit the changes. The title of the PR must be according to the pr-name skill.

Push the changes to the remote branch.
Use the gh CLI to create a pull request and use the same format as above for the title.