Guide an existing Remotion pull request through automated checks and merge it when eligible. Resolve conflicts, investigate failed checks, fix genuine problems, and use the flake skill to rerun checks that fail intermittently.
Wait for a Remotion pull request to become mergeable, handle merge conflicts, distinguish genuine CI failures from flakes, rerun flaky checks through the flake skill, and merge the PR. Use when asked to run /merge, merge a current PR after checks pass, or shepherd a Remotion PR through CI to merge.
Review the instructions the agent will receive before you install.
Use this skill for an existing pull request in the Remotion monorepo.
Start from the top after every pushed fix, conflict resolution, CI rerun, or other state change:
gh pr view --json number,url,state,isDraft,baseRefName,headRefName,mergeable,mergeStateStatus,reviewDecision,statusCheckRollup
If the PR is draft, closed, blocked by requested changes, missing required approval, or otherwise not eligible to merge for a non-CI reason, stop and report the blocker.
If GitHub reports merge conflicts, resolve them using the pr-ready workflow. Commit and push the resolution when needed, then start this loop from the top.
Wait for checks:
gh pr checks --watch --interval 30
gh pr merge --merge --delete-branch
If the repository or PR clearly requires another merge method, use that method instead.
When checks fail, inspect the failed jobs and logs before deciding what to do:
gh pr checks --watch=false
gh run view <run-id> --json databaseId,status,conclusion,url,jobs
gh run view <run-id> --log-failed
If it is a genuine CI failure:
pr-ready workflow when helpful.If it is a CI flake:
flake skill in this monorepo.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Add a reported Remotion bug to the bugs API with its affected versions, a short title, and upgrade guidance. Follow the existing entry format and place the new record first so recent bugs appear at the top.
Add a Remotion command-line or configuration option, or convert a hardcoded flag into a shared option definition. Connect parsing, configuration setters, help entries, and generated documentation so the option is consistently available and documented.
Add a new effect to @remotion/effects, including its implementation, package entry points, documentation, interactive demo, and preview images. Follow the package conventions and verify the changes with tests, formatting checks, and builds.
Add a person to the Remotion experts page by placing their portrait, entering their profile and contact links, and generating an expert card image. The instructions specify file locations, profile fields, and how to verify card generation.
Create a new @remotion package within the Remotion monorepo, a repository containing multiple packages. Set up its files, register it across the project, and prepare documentation, usage examples, and build configuration.
Add a new sound effect to @remotion/sfx, from registering the audio file to exporting its URL and documenting its use. The workflow covers playback examples, attribution, navigation entries, waveform generation, and the package build.