How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/remotion-dev/remotion --skill mergeBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
/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:
- Identify the PR:
bash
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:
bash
gh pr checks --watch --interval 30- If all required checks pass and the PR is mergeable, merge it:
bash
gh pr merge --merge --delete-branchIf 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:
bash
gh pr checks --watch=false
gh run view <run-id> --json databaseId,status,conclusion,url,jobs
gh run view <run-id> --log-failedIf it is a genuine CI failure:
- Fix the underlying issue locally, using the `pr-ready` workflow when helpful.
- Run the targeted local checks, plus broader checks when the change has broad impact.
- Commit and push the fix.
- Start the loop from the top.
If it is a CI flake:
- Use the `flake` skill in this monorepo.
- Rerun the failed flaky job or failed jobs as directed by that skill.
- Start the loop from the top.
