skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
remotion-dev/remotion853 installs

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.

How do I install this agent skill?

npx skills add https://github.com/remotion-dev/remotion --skill merge
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill is designed for managing pull requests within the Remotion monorepo. It uses the GitHub CLI to monitor CI checks, handle merge conflicts, and merge pull requests once they meet the necessary criteria. No malicious behavior was detected.

  • Socketpass

    No alerts

  • Snykwarn

    Risk: MEDIUM · 1 issue

What does this agent skill do?

/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:
gh pr view --json number,url,state,isDraft,baseRefName,headRefName,mergeable,mergeStateStatus,reviewDecision,statusCheckRollup
  1. 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.

  2. 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.

  3. Wait for checks:

gh pr checks --watch --interval 30
  1. If all required checks pass and the PR is mergeable, merge it:
gh pr merge --merge --delete-branch

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:

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:

  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 in a test file this PR added or changed, or a Web renderer flake test failure, treat it as a genuine failure: fix the test so it is deterministic, then push. Do not record it in the flake tracker and do not rerun it to get a green check.

If it is a CI flake in an existing test:

  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.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/remotion-dev/remotion/merge">View merge on skillZs</a>