merge-sweep

Automates merging of GitHub PRs and resolving blocking issues across repositories.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of managing pull requests across multiple repositories, automatically merging ready PRs and cleaning up those with blocking issues, significantly reducing manual overhead and accelerating development cycles.

Core Features & Use Cases

  • Automated Merging: Enables GitHub's auto-merge for PRs that meet all requirements.
  • Proactive Branch Updates: Updates stale branches on PRs to prevent merge deadlocks.
  • Automated PR Polishing: Fixes conflicts, CI failures, and review comments on blocking PRs.
  • Use Case: Run this skill nightly to clear the merge queue, ensuring that only merge-ready PRs are automatically merged and that blocking PRs are automatically fixed and re-evaluated.

Quick Start

Run the merge-sweep skill to automatically manage all open pull requests across your repositories.

Frequently Asked Questions about merge-sweep

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

FAQPage Schema
How do I automate GitHub pull request merging across multiple repositories?

Automating GitHub pull request merging is achieved by orchestrating the classification and merging of ready PRs across multiple repositories, resolving blocking issues to reduce manual overhead and accelerate CI/CD pipeline throughput.

How do I automatically fix merge conflicts and CI failures on blocking pull requests?

Automatically fixing merge conflicts and CI failures on blocking pull requests is handled by dispatching them to a PR polishing workflow, which resolves issues and re-evaluates the PRs for safe execution.

What is the best way to clear a nightly GitHub merge queue?

Clearing a nightly GitHub merge queue is best done by running an automated sweep that intelligently classifies PRs for direct auto-merging or proactive branch updates, ensuring only merge-ready PRs are processed.

Does automated PR merging work with stale branches and merge deadlocks?

Automated PR merging works with stale branches and merge deadlocks by proactively updating stale branches, handling complex scenarios like merge conflicts and CI failures with robust error handling and a claim registry.

Can I use automated branch updates to prevent merge deadlocks on GitHub?

Automated branch updates can be used to prevent merge deadlocks on GitHub by proactively updating stale branches on open PRs, ensuring branches remain current and reducing integration friction.

Why does automated PR merging classify pull requests into different workflows?

Automated PR merging classifies pull requests into different workflows to intelligently route them for proactive branch updates, direct auto-merging, or PR polishing, ensuring efficient CI/CD pipeline throughput and safe execution.