mergeability-gate

Evaluate GitHub Pull Request mergeability and apply status labels.

3|1|Updated Oct 9, 2025

Search Tags:#workflow #github #pr #labels #gate #ci #mergeability

Ready to run

npx skills add https://github.com/OmniNode-ai/omniclaude --skill mergeability-gate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mergeability-gate
Source: https://github.com/OmniNode-ai/omniclaude/tree/main/plugins/onex/skills/mergeability-gate
Command: npx skills add https://github.com/OmniNode-ai/omniclaude --skill mergeability-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the evaluation of a Pull Request's (PR) mergeability, ensuring code quality and adherence to project standards before merging. It prevents integration issues by identifying blocking problems or suggesting improvements.

Core Features & Use Cases

Automated Evaluation: Assesses PRs against predefined criteria for mergeability, potential splits, or blocking issues.
Labeling: Automatically applies GitHub labels (mergeable, needs-split, blocked) based on the evaluation.
Use Case: In a CI/CD pipeline, this Skill runs after local reviews and before the PR is created, providing immediate feedback on whether the PR is ready to merge, needs refactoring, or is blocked by critical issues like failing tests or merge conflicts.

Quick Start

Use the mergeability-gate skill to evaluate PR number 1234 in the OmniNode-ai/omnibase_core repository.

Frequently Asked Questions about mergeability-gate

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

FAQPage Schema

How do I automate GitHub PR mergeability checks in a CI pipeline?▼

Automating GitHub PR mergeability checks involves evaluating template compliance, CI status, merge conflicts, code complexity, and mixed concerns. The evaluation outputs a status of 'mergeable', 'needs-split', or 'blocked' and automatically applies corresponding GitHub labels to the PR.

What's the best way to automatically label a pull request as blocked or needs-split?▼

Automatically labeling a pull request as 'blocked' or 'needs-split' is done by inspecting CI status, merge conflicts, and code complexity against predefined criteria. When critical issues or mixed concerns are detected, the appropriate status label is applied directly to the PR via GitHub CLI.

Can I use GitHub CLI to inspect PR mergeability and apply labels automatically?▼

Yes, you can use GitHub CLI to inspect PR mergeability and apply labels automatically. The process utilizes GitHub CLI alongside internal libraries for PR inspection and mutation, evaluating predefined criteria to apply 'mergeable', 'needs-split', or 'blocked' labels.

What criteria should a pull request meet before being mergeable?▼

A pull request must meet criteria including template compliance, passing CI status, no merge conflicts, acceptable code complexity, and no mixed concerns. If these are satisfied, the PR receives a 'mergeable' status; otherwise, it is marked as 'needs-split' or 'blocked'.

Why would a pull request be marked as needs-split instead of mergeable?▼

A pull request is marked as 'needs-split' instead of 'mergeable' when the evaluation detects mixed concerns or high code complexity. This indicates the PR contains too many unrelated changes and should be refactored into smaller, focused PRs before merging.

When should I not use an automated PR mergeability gate?▼

You should not use an automated PR mergeability gate if your workflow relies entirely on manual human review without predefined structural criteria. This automation targets template compliance, CI status, and code complexity, and does not replace subjective code design evaluations.