Menu
Open a pull request for the current feature
Best practices for Remotion - Video creation in React
Manage GitHub Issues 2.0 relationships with gh CLI: parent issues, sub-issues, blocked-by, and blocking links.
Resolve CI failures, merge conflicts, or local branch changes to get a PR ready
Create or update GitHub issues with correct Remotion naming and safe multiline Markdown handling
Add a new effect to @remotion/effects, including implementation, package exports, docs, demos, preview images, Remotion skill updates, tests, formatting, and builds.
Add an interactive demo to the Remotion documentation. Use when creating a new <Demo> component for docs pages.
| name | 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
Then run
bun run build
bun run stylecheck
to ensure we compile and CI linting/formatting passes.
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.
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).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