check-merge

Check Pull Request merge readiness via GitHub CLI for conflicts, CI, and approvals.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/MJ-AgentLab/mj-agentlab-marketplace --skill check-merge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-merge
Source: https://github.com/MJ-AgentLab/mj-agentlab-marketplace/tree/main/plugins/mj-git/skills/mj-git-check-merge
Command: npx skills add https://github.com/MJ-AgentLab/mj-agentlab-marketplace --skill check-merge

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of checking if a Pull Request (PR) is ready to be merged by verifying critical criteria like merge conflicts, CI status, and review approvals.

Core Features & Use Cases

  • Merge Conflict Detection: Automatically checks if the PR has conflicts with the base branch.
  • CI Status Verification: Validates that all continuous integration checks have passed.
  • Review Status: Confirms if the necessary approvals have been obtained.
  • PR Description Completeness: Ensures the PR description meets required standards based on branch type.
  • Use Case: Before merging a feature branch, run this skill to ensure it won't break the main branch, all tests pass, and it has been approved by a reviewer.

Quick Start

Use the check-merge skill to see if the current PR is ready to merge.

Frequently Asked Questions about check-merge

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

FAQPage Schema
How do I check if a GitHub pull request is ready to merge?

To check if a pull request is ready to merge, you can automate the verification of merge conflicts, CI status, review approvals, and description completeness using GitHub CLI commands. This ensures code quality before integrating branches.

Can I automate GitHub PR merge conflict detection locally?

Yes, you can automate GitHub PR merge conflict detection locally by running a script that uses Git commands to interact with your local repository status and the GitHub CLI to query the base branch for conflicts.

Do I need GitHub CLI installed to verify PR review and CI status?

Yes, you need the GitHub CLI (`gh`) installed to verify PR review approvals and CI status. The tool relies on `gh` to interact with the GitHub API for checking continuous integration checks and reviewer feedback.

What is the best way to ensure PR description completeness before merging?

The best way to ensure PR description completeness is to use an automated check that validates the PR description against required standards based on the specific branch type before allowing the merge to proceed.

Why does my pull request fail continuous integration checks before merging?

Pull requests fail continuous integration checks when automated CI tests do not pass. Verifying CI status before merging ensures that failing checks are caught and addressed to prevent breaking the main branch.