Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →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.
Passed 8 of 15 test cases with the skill, and 6 of 15 without it.
and 5 more in the full report
6 fixed6 passed either way9 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
PR #2040 in Remotion is fully green and approved. I usually run `gh pr merge --squash --delete-branch` to keep a clean linear history. Which merge strategy parameter should be used for Remotion PRs by default?
| Checked | Without skill | With skill |
|---|---|---|
| Uses --merge flag instead of --squash. | Missed | Passed |
| Includes --delete-branch flag. | Passed | Passed |
The instructions your model reads when the skill loads.
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
test cases passed, vs 6 / 15 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.