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

96%

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

100%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 short-form skill body: concise, fully actionable, with a clear looped workflow and explicit validation/feedback checkpoints for a destructive merge operation. Organization is clean and references are one level deep.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout — executable `gh` commands with no padding, no explanation of concepts Claude already knows, and every line earns its place.	5 / 5
Actionability	Fully executable, copy-paste-ready `gh pr view`, `gh pr checks`, `gh pr merge`, and `gh run view` commands cover the common cases; only the inherent `<run-id>` placeholder requires substitution.	5 / 5
Workflow Clarity	A clearly sequenced loop with explicit restart-after-each-change semantics, validation checkpoints (draft/blocker detection, checks-watch, inspect-failed-logs-before-acting), and feedback loops (fix→push→restart, flake→rerun→restart) for the destructive merge operation.	5 / 5
Progressive Disclosure	A compact, single-purpose skill (~55 lines) with well-organized sections (Loop, CI Failures) and one-level-deep, clearly signaled cross-skill links to pr-ready and flake; no bundle files needed.	5 / 5
	Total	20 / 20 Passed

Description

92%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, specific description that clearly states both capabilities and trigger conditions with a well-defined niche. It is concise yet comprehensive, with only minor room for additional trigger synonyms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Wait for a Remotion pull request to become mergeable, handle merge conflicts, distinguish genuine CI failures from flakes, rerun flaky checks... and merge the PR' — giving comprehensive coverage of what the skill does.	5 / 5
Completeness	Explicitly answers both what ('Wait for...merge the PR' with concrete sub-actions) and when ('Use when asked to run /merge, merge a current PR after checks pass, or shepherd a Remotion PR through CI to merge').	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('run /merge', 'merge a current PR after checks pass', 'shepherd a Remotion PR through CI to merge') with good coverage, though it lacks broader synonym variations.	4 / 5
Distinctiveness Conflict Risk	Scoped to 'Remotion pull request' with distinct triggers (/merge, shepherd through CI), giving it a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	19 / 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: 19ec0ee

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