Pr
- 461 installs
- 55.5k repo stars
- Updated August 4, 2026
- remotion-dev/remotion
Open a Remotion monorepo pull request after format, build, and stylecheck with a pr-name-compliant title and safe gh body-file flow.
About
pr is a Remotion repository workflow skill that turns finished feature work into a review-ready GitHub pull request. It enforces branch hygiene away from main, formats touched packages with Oxfmt, and runs the same build and stylecheck gates CI expects before commit and push. Titles must conform to the separate pr-name skill so release and changelog automation stay predictable. For the PR body, the skill deliberately avoids passing Markdown through fragile inline shell arguments, instructing agents to write a temp file such as /tmp/remotion-pr-body.md and call gh pr create with --body-file. Solo builders contributing patches to Remotion—or agents acting on their behalf—use this to reduce rejected PRs from formatting drift or malformed titles.
- Blocks direct commits on main by requiring a feature branch first
- Runs bunx oxfmt src --write on affected packages before CI
- Requires bun run build and bun run stylecheck before push
- PR title must follow the pr-name skill; body supplied via --body-file not inline shell strings
Pr by the numbers
- 461 all-time installs (skills.sh)
- +61 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #109 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/remotion-dev/remotion --skill prAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 461 |
|---|---|
| repo stars | ★ 55.5k |
| Last updated | August 4, 2026 |
| Repository | remotion-dev/remotion ↗ |
What it does
Open a Remotion monorepo pull request after format, build, and stylecheck with a pr-name-compliant title and safe gh body-file flow.
Files
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 --writeThen 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. 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). 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.mdRelated skills
Caveman CommitGenerate terse, Conventional Commits messages that preserve intent without fluff or AI attribution.272k94k
Resolving Merge ConflictsQuickly understand, resolve, and commit merge conflicts without losing work or breaking their flow.183k193kGit Guardrails Claude CodePrevent Claude Code from accidentally running destructive git commands like force push, hard reset, or clean.175k193k
Using Git WorktreesGuarantee every new feature or implementation task runs inside a clean, isolated workspace without polluting the main branch or current working directory.149k263k
Git CommitGenerate accurate conventional commit messages and intelligently stage files directly from natural language requests.40.6k37.2k
Resolve Merge ConflictsQuickly understand and resolve Git merge conflicts without losing context or breaking changes.16.5k148