How do I install the Gh Merge skill?

Run npx skillmds@latest add agentsmesh/gh-merge in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gh Merge safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gh Merge?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gh Merge free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gh Merge?

AgentsMesh (@agentsmesh) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gh Merge by agentsmesh — Agent Skill

Name: Gh Merge
Rating: 4.2 (5 reviews)
Author: AgentsMesh

Gh Merge

Completes the AgentsMesh GitHub pull-request workflow: commits scoped changes, rebases on the authoritative GitHub branch, opens or reuses a PR, monitors required checks, fixes failures, and merges only after verification. Use when the user asks to merge, submit, or land repository changes.

AgentsMesh Updated Sep 10, 2026

File contents

GitHub Merge

GitHub is the development source of truth for this repository. Land changes through a GitHub pull request; do not create a GitLab merge request for product code.

Workflow

Inspect repository state:

git status --short --branch
git branch --show-current
git remote -v
gh auth status --hostname github.com

Identify the GitHub remote by URL instead of assuming a remote name. Resolve the target branch, normally main, and refuse to merge directly while checked out on that branch.
Review all dirty files. Stage only files belonging to the requested change; preserve unrelated user changes and never use git add .. Run the relevant local tests and git diff --check, then create a focused commit containing only the requested change.
Require a clean index and working tree before rebasing. If unrelated user changes remain, do not stash or move them automatically; use an already isolated checkout or stop and report what prevents a safe rebase. Once the checkout is clean, fetch and rebase on the current GitHub target:
```
git fetch <github-remote> <target-branch>
git rebase <github-remote>/<target-branch>
```
Resolve conflicts with user-owned work preserved, then rerun affected tests when the rebase changes the integration base.
Push the current branch. After a rebase, use --force-with-lease, never --force.
Reuse an existing pull request for the branch or create one with gh pr create and the repository PR template. The title and body must explain behavior, verification, and any remaining risk.
Inspect review state and wait for checks:
```
gh pr checks <pr-number> --watch --interval 15 --fail-fast
```
At least one check must be observed. If no checks are reported, retry after the workflow trigger delay; no checks is not a passing state. Diagnose failures from run logs, fix them, push, and monitor again.
Merge only when all observed checks have completed successfully, reviews and branch policy allow it, and the PR is conflict-free:
```
gh pr merge <pr-number> --squash --delete-branch
```
Verify the remote PR state is MERGED. In a worktree, failure to delete the local branch does not mean the remote merge failed; report cleanup separately.

Result

Report the PR URL, source and target branches, commit, local tests, remote check results, merge method, and any local branch or worktree that remains.

---name: gh-mergedescription: Completes the AgentsMesh GitHub pull-request workflow: commits scoped changes, rebases on the authoritative GitHub branch, opens or reuses a PR, monitors required checks, fixes failures, and merges only after verification. Use when the user asks to merge, submit, or land repository changes.---# GitHub MergeGitHub is the development source of truth for this repository. Land changesthrough a GitHub pull request; do not create a GitLab merge request for productcode.## Workflow1. Inspect repository state: ```bash git status --short --branch git branch --show-current git remote -v gh auth status --hostname github.com ```2. Identify the GitHub remote by URL instead of assuming a remote name. Resolve the target branch, normally `main`, and refuse to merge directly while checked out on that branch.3. Review all dirty files. Stage only files belonging to the requested change; preserve unrelated user changes and never use `git add .`. Run the relevant local tests and `git diff --check`, then create a focused commit containing only the requested change.4. Require a clean index and working tree before rebasing. If unrelated user changes remain, do not stash or move them automatically; use an already isolated checkout or stop and report what prevents a safe rebase. Once the checkout is clean, fetch and rebase on the current GitHub target: ```bash git fetch <github-remote> <target-branch> git rebase <github-remote>/<target-branch> ``` Resolve conflicts with user-owned work preserved, then rerun affected tests when the rebase changes the integration base.5. Push the current branch. After a rebase, use `--force-with-lease`, never `--force`.6. Reuse an existing pull request for the branch or create one with `gh pr create` and the repository PR template. The title and body must explain behavior, verification, and any remaining risk.7. Inspect review state and wait for checks: ```bash gh pr checks <pr-number> --watch --interval 15 --fail-fast ``` At least one check must be observed. If no checks are reported, retry after the workflow trigger delay; no checks is not a passing state. Diagnose failures from run logs, fix them, push, and monitor again.8. Merge only when all observed checks have completed successfully, reviews and branch policy allow it, and the PR is conflict-free: ```bash gh pr merge <pr-number> --squash --delete-branch ```9. Verify the remote PR state is `MERGED`. In a worktree, failure to delete the local branch does not mean the remote merge failed; report cleanup separately.## ResultReport the PR URL, source and target branches, commit, local tests, remote checkresults, merge method, and any local branch or worktree that remains.

Frequently asked questions