skills.rest
OmniNode-ai
OmniNode-aiOFFICIAL
Explore all skills by this author →
GitHub

integration-gate

Orchestrate cross-repository pull request merging into GitHub's Merge Queue.

3|1|Updated Oct 9, 2025
Search Tags:#automation#git#workflow#ci/cd#github actions#merge queue
One-click install
npx skills add https://github.com/OmniNode-ai/omniclaude --skill integration-gate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: integration-gate
Source: https://github.com/OmniNode-ai/omniclaude/tree/main/plugins/onex/skills/integration-gate
Command: npx skills add https://github.com/OmniNode-ai/omniclaude --skill integration-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of merging pull requests across multiple repositories by intelligently classifying them, enforcing dependencies, and integrating with GitHub's Merge Queue, ensuring a stable and ordered release process.

Core Features & Use Cases

  • Automated Lane Classification: Classifies PRs into 'fast', 'standard', or 'high_risk' based on labels and file paths.
  • Cross-Repo Dependency Management: Detects and enforces dependencies between PRs in different repositories using topological sorting.
  • GitHub Merge Queue Integration: Enqueues PRs into the GitHub Merge Queue with respect to lane policies and dependencies.
  • Slack Gate Approval: Provides a mechanism for manual approval for high-risk changes via Slack.
  • Use Case: A team managing a microservices architecture can use this skill to ensure that backend API changes are merged and deployed before frontend changes that depend on them, preventing integration issues.

Quick Start

Run the integration-gate skill to scan all repositories and enqueue merge-ready pull requests into the GitHub Merge Queue.

Frequently Asked Questions about integration-gate

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

FAQPage Schema
How do I automate cross-repo pull request merging into a GitHub Merge Queue?▼

Cross-repo PR merging is automated by orchestrating pull requests into GitHub's Merge Queue using lane classification, topological dependency sorting, and optional Slack gate approvals to ensure stable, ordered releases across multiple repositories.

What is topological ordering for cross-repository dependencies in CI/CD workflows?▼

Topological ordering detects and enforces dependencies between pull requests in different repositories. It ensures prerequisite changes, such as backend API updates, are merged before dependent frontend changes to prevent integration issues.

Can I require manual Slack approval for high-risk pull requests before they merge?▼

Yes, you can require manual approval for high-risk changes via a Slack gate. The skill classifies PRs into 'fast', 'standard', or 'high_risk' lanes, triggering Slack approval mechanisms specifically for high_risk entries before enqueueing.

How do I handle PR ejection and retries in a GitHub Merge Queue?▼

PR ejection is handled with lane-specific retry policies during queue monitoring. When a PR is ejected, the skill applies retry rules based on whether the PR was classified into the 'fast', 'standard', or 'high_risk' lane.

How are pull requests classified into merge lanes based on labels and file paths?▼

Pull requests are classified into 'fast', 'standard', or 'high_risk' lanes by evaluating repository labels and file paths. This automated lane classification determines queue policies, retry behavior, and whether Slack approval is required.

Related Skills

Explore More Software Engineering Skills→
rysweetrysweet
2

Creating Pull Requests

Analyze commits and diffs to generate structured pull request descriptions.

Community
Intermediate
pertain99pertain99
1

github

Fetch GitHub issues, PRs, and CI status using the gh CLI.

Community
Intermediate
cobusgreylingcobusgreyling
10.0k

pr-review-triage

Monitor pull requests for status, merge conflicts, and unanswered comments.

Community
Intermediate
rioX432rioX432
2

dev-all

Processes GitHub issues sequentially with dependency ordering and CI-gated PR merges.

Community
Advanced