auto-merge

Merge GitHub pull requests after CDQA checks and Slack approvals.

3|1|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/OmniNode-ai/omniclaude --skill auto-merge-omninode-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-merge
Source: https://github.com/OmniNode-ai/omniclaude/tree/main/plugins/onex/skills/auto-merge
Command: npx skills add https://github.com/OmniNode-ai/omniclaude --skill auto-merge-omninode-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of merging GitHub Pull Requests (PRs) once all predefined checks and approvals are met, streamlining the CI/CD pipeline and reducing manual intervention.

Core Features & Use Cases

  • Automated Merging: Merges PRs using specified strategies (squash, merge, rebase).
  • Gate Enforcement: Integrates with Slack for manual HIGH_RISK approval before merging.
  • Dependency Checks: Ensures Continuous Delivery and Quality Assurance (CDQA) gates pass before proceeding.
  • Ticket Management: Optionally closes associated Linear tickets upon successful merge.
  • Use Case: Automatically merge a feature branch into main after all automated tests pass, a code review is approved, and a product manager gives a final "merge" confirmation via Slack.

Quick Start

Use the auto-merge skill to merge pull request number 123 in the repository owner/repo repository.

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 a GitHub pull request after CI checks pass?

You can automatically merge a GitHub pull request by orchestrating CDQA gate checks, Slack-based approvals, and conditional Linear ticket closure. The process enforces CI readiness and review status compliance before executing the merge.

Can I require a Slack approval before merging high-risk pull requests?

Yes, Slack-based manual approval is enforced for HIGH_RISK pull requests before merging. This gate mechanism ensures product managers or reviewers provide a final confirmation via Slack, preventing unauthorized automated merges.

What GitHub merge strategies are supported for automated PR merging?

Automated PR merging supports configurable merge strategies including squash, merge, and rebase. You can specify the desired strategy to merge feature branches into target branches like main once all checks pass.

Does automated PR merging work with Linear ticket management?

Yes, automated PR merging integrates with Linear by optionally closing associated Linear tickets upon successful merge. This ensures your project management tracking stays synchronized with your GitHub repository changes.

How do I configure branch deletion policies after a GitHub PR is merged?

Branch deletion policies are configurable within the automated merge process. After a GitHub PR is successfully merged using your specified strategy, the feature branch can be automatically deleted based on your configured settings.

What are the limitations of automating GitHub PR merges with Slack gates?

Automating GitHub PR merges requires CDQA gates to pass and Slack approvals for HIGH_RISK changes before execution. If Continuous Delivery or Quality Assurance checks fail, or Slack confirmation is denied, the merge will not proceed.