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.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplary lean, fully executable skill body: every instruction is a runnable gh command, the loop restart rule keeps state changes coherent, and validation checkpoints plus fix/retry feedback loops are explicit. The single notable gap is that the genuine-failure-vs-flake decision — the skill's own stated purpose — has no criteria, heuristics, or examples to guide it.

Suggestions

Add 2–3 concrete heuristics or examples for distinguishing a genuine CI failure from a flake (e.g. failure reproduces locally / error is in changed code vs. timeout, network, or test-unrelated job), since this decision drives which branch of the workflow runs.

Clarify how to obtain the `<run-id>` used in `gh run view` (e.g. from `gh pr checks --watch=false` output) so the CI-failure inspection path is fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	Every line is a step, an executable gh command, or a clearly signaled delegation to a sibling skill; there is no concept explanation or padding at all, matching the lean-and-efficient anchor.	5 / 5
Actionability	Commands are copy-paste ready and complete (`gh pr view --json ...`, `gh pr checks --watch --interval 30`, `gh pr merge --merge --delete-branch`, `gh run view <run-id> --log-failed`), but the pivotal decision — distinguishing a genuine CI failure from a flake — gets only "inspect the failed jobs and logs before deciding what to do" with no criteria or heuristics, leaving a common case without executable guidance. Not 3 because everything that is given is fully executable.	4 / 5
Workflow Clarity	The loop has explicit validation checkpoints (eligibility/blocker check in step 2, "all required checks pass and the PR is mergeable" in step 5) and genuine feedback loops — genuine failure → fix → push → restart, flake → rerun → restart — with an explicit "start from the top after every state change" rule. Not 4 because the checkpoints are explicit rather than implicit.	5 / 5
Progressive Disclosure	No bundle files exist or are needed at this size; the two sections are well-organized and the only references — [`pr-ready`](../pr-ready/SKILL.md) and [`flake`](../flake/SKILL.md) — are sibling skills referenced one level deep with clear link signals, satisfying the well-organized-sections bar for a short skill with no separate-file content.	5 / 5
	Total	19 / 20 Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete, third-person, and comprehensive on both capabilities and triggers, with an explicit "Use when" clause covering the slash command and the natural user phrasings. The only weakness is minor overlap risk with a generic merge skill and a few missing natural trigger synonyms.

Dimension	Reasoning	Score
Specificity	Lists five concrete actions spanning the full lifecycle — "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" — matching the comprehensive-coverage anchor; not 4 because no part of the workflow is left uncovered.	5 / 5
Completeness	Explicitly answers both questions: a concrete "what" in the first sentence and a concrete trigger clause — "Use when asked to run /merge, merge a current PR after checks pass, or shepherd a Remotion PR through CI to merge". Not 4 because the "when" is specific, not merely present.	5 / 5
Trigger Term Quality	Good natural coverage — "merge", "PR"/"pull request" as a synonym pair, "checks pass", "CI", "run /merge", "Remotion" — but a few phrases a user would naturally say (e.g. "handle merge conflicts", "CI is failing", "flake") are absent, so it falls just short of the comprehensive synonym-level anchor.	4 / 5
Distinctiveness Conflict Risk	Clear Remotion-scoped niche with the distinct "/merge" trigger, but "merge a current PR after checks pass" could also match a generic PR-merge skill, giving minor overlap risk with closely related skills. Not 3 — the flake/conflict/CI-shepherding scope is genuinely distinct from generic merge helpers.	4 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 3 suspicious	Warning

	Total	15 / 16 Passed

Repository: remotion-dev/remotion
Path: .agents/skills/merge/SKILL.md
Commit: 6f4e0d5

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.