Auto Merge

Automate merging pull requests that pass CI and safety gates.

Updated Jun 2, 2026

Search Tags:#automation #github #code-review #ci #auto-merge #pull-requests #merge-safety

Ready to run

npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill auto-merge-atrium-hermes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Auto Merge
Source: https://github.com/Atrium-Hermes/atrium-lighthouse/tree/main/skills/auto-merge
Command: npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill auto-merge-atrium-hermes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automatically merges pull requests that have passing CI, no blocking reviews, and no conflicts, reducing manual overhead and speeding delivery.

Core Features & Use Cases

Enforces safety gates: author allowlists, size caps, proper base branches, and complete checks before merging.
Supports dry-run mode to simulate merges without changing state.
Scales across multiple repositories by processing open PRs in watched repos and clearing backlogs.

Quick Start

Enable auto-merge on watched repositories and let it process all open PRs that pass CI.

Frequently Asked Questions about Auto Merge

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

FAQPage Schema

How do I auto-merge GitHub pull requests that pass CI?▼

To auto-merge GitHub pull requests that pass CI, this skill processes open PRs in watched repositories, verifying passing checks, no blocking reviews, and no conflicts before merging. It applies author allowlists and base-branch safety policies.

What is merge safety in automated pull request workflows?▼

Merge safety in automated pull request workflows means enforcing author allowlists, size caps, proper base branches, and complete CI check statuses before allowing a merge. This prevents unauthorized or broken code from reaching protected branches.

Can I simulate auto-merging pull requests without changing repository state?▼

Yes, you can simulate auto-merging pull requests without changing repository state by enabling the configurable dry-run mode. This processes open PRs against safety gates and CI checks to validate readiness without performing the actual merge.

Does auto-merge work across multiple watched GitHub repositories?▼

Yes, auto-merge works across multiple watched GitHub repositories by processing open PRs and clearing backlogs. It uses memory-based per-PR tracking to manage merge queues and ensures safety gates are enforced across all repos.

What are the limitations of automating pull request merges based on CI status?▼

Automating pull request merges based on CI status requires no blocking reviews and no conflicts. Limitations include blocking PRs that exceed size caps or target improper base branches, necessitating manual intervention to resolve these safety policy violations.