Auto Merge

Merge open pull requests that pass CI and safety checks.

Updated Jun 3, 2026

Search Tags:#automation #github #merge #ci #pull-request #safety-policy

Ready to run

npx skills add https://github.com/swarm-ai-research/aeon --skill auto-merge-swarm-ai-research

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Auto Merge
Source: https://github.com/swarm-ai-research/aeon/tree/main/skills/auto-merge
Command: npx skills add https://github.com/swarm-ai-research/aeon --skill auto-merge-swarm-ai-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the safe merging of open pull requests that pass CI, do not require blocking reviews, and have no conflicts, eliminating repetitive manual merging and speeding up integration.

Core Features & Use Cases

Automated PR merging when all safety criteria are met, including author allowlist, size caps, and mergeability checks.
Enforcement of per-PR safety policy across watched repositories to prevent unsafe merges.
Per-run and cross-run state tracking with retry logic to handle transient failures and avoid re-merging.

Quick Start

Run auto-merge on all watched repositories for open PRs that pass CI and safety checks.

Frequently Asked Questions about Auto Merge

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

FAQPage Schema

How do I automatically merge GitHub pull requests that pass CI checks?▼

Automatically merging GitHub pull requests that pass CI checks requires evaluating per-PR eligibility based on base branch, mergeStateStatus, author allowlist, drafts, and checks status. This skill merges open PRs meeting defined safety policies into target branches to automate code integration.

What is the safest way to automate PR merging across watched repositories?▼

Safe PR merging across watched repositories is achieved by enforcing per-PR safety policies, author allowlists, size caps, and mergeability checks. The system evaluates pull request eligibility and logs outcomes while persisting state in memory to avoid re-merging and handle transient failures.

Can I use an author allowlist to control which pull requests auto-merge?▼

Using an author allowlist to control auto-merging allows you to restrict automated integration to trusted bot-authored pull requests or specific contributors. The skill evaluates per-PR eligibility based on the author allowlist alongside CI checks and mergeability status before merging.

How does auto-merge handle pull requests with transient CI failures or merge conflicts?▼

Handling pull requests with transient CI failures involves per-PR retry logic and cross-run state tracking. The skill skips PRs with merge conflicts or failing checks, retries eligible PRs during transient failures, and enforces per-run caps to prevent unsafe merges while persisting state in memory for continuity.

Does auto-merge work with draft pull requests and bot-authored PRs?▼

Auto-merge works with bot-authored PRs by evaluating them against author allowlists and safety policies, but it skips draft pull requests. It evaluates per-PR eligibility based on drafts, base branch, mergeStateStatus, and checks status to decide whether to merge or skip across watched repositories.