skills.rest
shawn-sandy
shawn-sandyCOMMUNITY
Explore all skills by this author →
Website𝕏@shawnsandyGitHub

merge

Verifies pull request readiness gates and merges approved PRs via GitHub CLI.

Updated Jun 8, 2026
Search Tags:#git#code review#pull request#github#merge#gh cli#ci checks
One-click install
npx skills add https://github.com/shawn-sandy/agentics-kit --skill merge-shawn-sandy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge
Source: https://github.com/shawn-sandy/agentics-kit/tree/main/kit/plugins/git-agent/skills/merge
Command: npx skills add https://github.com/shawn-sandy/agentics-kit --skill merge-shawn-sandy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merging a pull request safely requires checking CI status, review decisions, merge conflicts, and branch protection rules — doing this manually is error-prone and easy to get wrong. This Skill automates the readiness gate and only merges after explicit user approval, preventing accidental merges of failing or unreviewed code. ## Core Features & Use Cases - Readiness Gate: Checks mergeable state, mergeStateStatus, required CI checks, and review decisions before allowing any merge. - Safe Merge Execution: Pins the merge to the verified commit using --match-head-commit so late-arriving commits never slip in silently. - CI Diagnostics: Distinguishes between CI that never dispatched (billing or quota blocks) and genuine failures, so red checks are reported accurately. - Use Case: After your PR passes review, ask "is my PR ready to merge?" — the Skill checks all gates, shows you a full status summary, and merges only after you confirm. ## Quick Start Ask the assistant to check whether the current branch's pull request is ready to merge and merge it if everything is green.

Frequently Asked Questions about 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?▼

Run gh pr view to read mergeable, mergeStateStatus, and reviewDecision, then gh pr checks --required to verify required CI checks pass. A PR is ready when mergeable is MERGEABLE, all required checks succeed, and no changes are requested.

How to merge a pull request safely with GitHub CLI?▼

Use gh pr merge with --squash and --match-head-commit to pin the merge to the exact commit you verified. This makes the merge fail rather than silently landing commits pushed after your verification.

Does this work with GitLab merge requests?▼

Yes, the same gates apply on GitLab using glab commands: glab mr view for pipeline and state, then glab mr merge after approval. Unresolved discussions are reported but not treated as a blocking gate.

Why does gh pr checks show nothing when CI should have run?▼

An empty check list can mean CI never dispatched due to billing blocks, expired tokens, or workflows awaiting approval. Verify with gh run list --commit to see whether any jobs actually started before concluding checks passed.

What are the limitations of automated PR merging?▼

This Skill does not commit, push, or create PRs — those must happen first. It never deletes branches automatically, will not merge with failing required checks or requested changes, and always requires explicit user approval.

Related Skills

Explore More Software Engineering Skills→
eriknovakeriknovak

commit-pr

Create a conventional commit, push the branch, and open a GitHub pull request.

Community
Advanced
panayiotismpanayiotism
79

merge

Merge open pull requests in dependency order and clean up branches.

Community
Advanced
yanochka11yanochka11

iterate-pr

Iterate pull requests by resolving CI failures and review feedback until validation succeeds.

Community
Advanced
netresearchnetresearch
8

github-project

Automate GitHub repository setup and branch protection configuration.

Official
Advanced