skills.rest
enuno
enunoCOMMUNITY
Explore all skills by this author →
Website𝕏@NunoElvisGitHub

Auto Merge

Merge pull requests that pass safety policy checks.

Updated Jul 16, 2026
Search Tags:#CI/CD#GitHub#auto-merge#safety policy#PR merging
One-click install
npx skills add https://github.com/enuno/noesis-aeon --skill auto-merge-enuno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Auto Merge
Source: https://github.com/enuno/noesis-aeon/tree/main/skills/auto-merge
Command: npx skills add https://github.com/enuno/noesis-aeon --skill auto-merge-enuno

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of merging pull requests that meet specific criteria, reducing manual effort and speeding up the release process.

Core Features & Use Cases

  • Automated PR Merging: Merges pull requests that have passing continuous integration, no blocking reviews, and no conflicts.
  • Safety Policy: Enforces a safety policy to prevent accidental merges of PRs that could lead to issues.
  • Use Case: Use this Skill to automatically merge PRs that have been reviewed and are ready to be integrated into the main branch.

Quick Start

Run the Auto Merge skill on the current branch.

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 with passing CI?▼

Auto merging evaluates pull requests against a safety policy including author allowlists, size caps, and mergeable state checks. It prevents accidental merges of PRs that could lead to issues by strictly enforcing these criteria before integration.

How does auto-merge handle conflicts and blocking reviews on pull requests?▼

Auto-merge skips pull requests with conflicts or blocking reviews to maintain branch stability. It only processes PRs that have passing continuous integration and a clean mergeable state according to the configured safety policy.

Can I restrict automated PR merging to specific authors?▼

Yes, you can restrict automated merging by using an author allowlist policy. This ensures only pull requests created by approved contributors are merged automatically, preventing unauthorized changes to the main branch.

What is the best way to enforce a safety policy before merging PRs?▼

The best way to enforce a safety policy is by applying strict checks like size caps and mergeable state validations. This prevents accidental merges of pull requests that could lead to issues in your software development workflow.

When should I not use automated PR merging in CI/CD workflows?▼

You should not use automated PR merging when pull requests require manual intervention or complex conflict resolution. If a PR fails the size cap, author allowlist, or mergeable state checks, it will be bypassed to prevent breaking the main branch.

Related Skills

Explore More Software Engineering Skills→
mvillmowmvillmow
18

verify-pr-ready

Verify GitHub pull requests for CI checks, approvals, and merge conflicts.

Community
Basic
tachiiri-orgtachiiri-org

release

Create a pull request from the dev branch to main after verifying branch and remote state.

Official
Intermediate
GenproMMGenproMM

gsd-ship

Automate pull request creation, review triggering, and merge tracking in Git repositories.

Official
Intermediate
26mitch2626mitch26

finishing-a-development-branch

Guide development branch completion with tests, merge, pull request, or cleanup options.

Community
Intermediate