gh-merge

Automate GitHub Pull Request creation, CI monitoring, and merging.

2.3k|237|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/AgentsMesh/AgentsMesh --skill gh-merge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-merge
Source: https://github.com/AgentsMesh/AgentsMesh/tree/main/.claude/skills/gh-merge
Command: npx skills add https://github.com/AgentsMesh/AgentsMesh --skill gh-merge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of merging code into GitHub repositories by automating the creation of Pull Requests, monitoring CI checks, and handling potential conflicts or failures until a successful merge.

Core Features & Use Cases

  • Automated PR Creation: Creates Pull Requests to merge the current branch into a target branch (e.g., main, develop).
  • CI/CD Monitoring: Automatically waits for and monitors GitHub Actions CI checks, ensuring they pass before merging.
  • Conflict Resolution: Provides guidance and commands to resolve merge conflicts and rebase operations.
  • Use Case: A developer finishes a new feature on a separate branch. They can invoke this Skill to automatically create a PR, ensure all tests pass, and merge it into the main branch without manual intervention.

Quick Start

Run /gh-merge to merge the current branch into the main branch.

Frequently Asked Questions about gh-merge

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

FAQPage Schema
How do I automate GitHub Pull Request creation and CI check monitoring before merging?

Automating GitHub Pull Request creation and CI check monitoring involves creating a PR from your current branch and waiting for GitHub Actions CI checks to pass. This Skill handles the entire lifecycle automatically, ensuring CI passes before merging into the target branch.

How do I handle merge conflicts and rebase operations when automating a GitHub PR merge?

Handling merge conflicts and rebase operations during an automated PR merge requires robust error handling. This Skill provides specific commands to resolve conflicts and performs force pushes with lease to safely update your remote branch.

Do I need the gh CLI installed to automate GitHub PR merges?

Yes, you need the gh CLI installed to automate GitHub PR merges. This Skill relies on the gh dependency to interact with GitHub repositories, create pull requests, and monitor CI/CD status directly from your environment.

What happens if GitHub Actions CI checks fail or report no status during an automated merge?

If GitHub Actions CI checks fail or report no status during an automated merge, the process halts to prevent broken code integration. This Skill includes robust error handling for common issues like CI failures and no checks reported.

Can I automatically merge a feature branch into the main branch after all tests pass?

Yes, you can automatically merge a feature branch into the main branch after all tests pass. By invoking this Skill, it creates the PR, monitors GitHub Actions CI checks, and completes the merge into your target branch without manual intervention.