Agent skill · software engineering · remotion-dev
merge
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.
Why this skill is useful
Adds a comprehensive automation script for managing pull requests in the Remotion monorepo, including conflict resolution and CI handling.
What it needs
Requires gh installed locally. About 1k tokens when loaded. Last updated 2026-08-06. 55,698 stars on the source repository.
What this skill does
/merge Use this skill for an existing pull request in the Remotion monorepo. Loop Start from the top after every pushed fix, conflict resolution, CI rerun, or other state change: 1. Identify the PR: 2. 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. 3. 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. 4. Wait for checks: 5. If all required checks pass and the PR is mergeable, merge it: If the repository or PR clearly requires another merge method, use that method instead. CI Failures When checks fail, inspect the failed jobs and logs before deciding what to do: If it is a genuine CI failure: 1. Fix the underlying issue locally, using the pr-ready workflow when helpful. 2. Run the targeted local checks, plus broader checks when the change has broad impact. 3. Commit and push the fix. 4. Start the loop from the top. If it is a CI flake: 1. Use the flake skill in this monorepo. 2. Rerun the failed flaky job or failed jobs as directed by that skill. 3. Start the loop from the top.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills remotion-dev/merge