skills.rest
danielbere1973
danielbere1973COMMUNITY
Explore all skills by this author →
GitHub

merge

Monitors Remotion pull requests, resolves conflicts and CI failures, then merges them.

Updated May 15, 2026
Search Tags:#automation#pull request#github#merge#gh cli#ci#remotion
One-click install
npx skills add https://github.com/danielbere1973/promoar --skill merge-danielbere1973
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge
Source: https://github.com/danielbere1973/promoar/tree/main/.agents/skills/merge
Command: npx skills add https://github.com/danielbere1973/promoar --skill merge-danielbere1973

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shepherding a pull request through CI to a successful merge involves repetitive manual work: watching checks, distinguishing flaky failures from real bugs, resolving merge conflicts, and rerunning jobs. This Skill automates that entire loop for Remotion monorepo PRs. ## Core Features & Use Cases - Merge Readiness Loop: Continuously inspects PR state with the GitHub CLI, blocking on drafts, missing approvals, or requested changes before attempting a merge. - Conflict and Failure Handling: Resolves merge conflicts via the pr-ready workflow, fixes genuine CI failures locally, and reruns flaky checks through the flake skill. - Automated Merge: Squash-merges the PR and deletes the branch once all required checks pass. - Use Case: You open a Remotion PR and ask the agent to merge it. The skill watches CI, reruns a flaky test job, pushes a fix for a real lint failure, and finally squash-merges the PR without further intervention. ## Quick Start Run /merge to watch my current Remotion pull request, handle any CI failures or conflicts, and merge it once checks pass.

Frequently Asked Questions about merge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically merge a GitHub pull request after checks pass?▼

Use the gh CLI to watch checks with gh pr checks --watch, verify the PR is mergeable via gh pr view, then run gh pr merge --squash --delete-branch. This skill automates that loop for Remotion PRs, including failure handling.

How to tell flaky CI failures from real test failures on GitHub?▼

Inspect the failed jobs with gh run view --log-failed and examine the logs before deciding. Genuine failures require a local fix and push, while flakes should be rerun using the flake skill rather than changing code.

How do I resolve merge conflicts in a pull request from the command line?▼

When GitHub reports conflicts, follow the pr-ready workflow to resolve them locally, then commit and push the resolution. After pushing, re-check the PR state and restart the merge monitoring loop.

Can this skill merge draft PRs or PRs with requested changes?▼

No. If the PR is a draft, closed, blocked by requested changes, or missing required approval, the skill stops and reports the blocker instead of merging. It only proceeds when the PR is eligible.

What merge method does this skill use for pull requests?▼

It uses gh pr merge --squash --delete-branch by default, squashing commits and removing the head branch. If the repository or PR clearly requires a different merge method, that method is used instead.

Related Skills

Explore More Software Engineering Skills→
eriknovakeriknovak

commit-pr

Create a conventional commit, push the branch, and open a GitHub pull request.

Community
Advanced
paywherebpaywhereb

prune-merged-branches

Prune local git branches verified as merged via GitHub PR head SHAs.

Official
Advanced
remotion-devremotion-dev
57.9k

merge

Shepherd Remotion pull requests through CI checks and merge them.

Official
Intermediate
overviewlabsoverviewlabs

github-pr-workflow

Automate GitHub pull request lifecycle from branch creation to merge.

Community
Advanced