skills.rest
alistairhendersoninfo
alistairhendersoninfoCOMMUNITY
Explore all skills by this author →
GitHub

merge-pr

Merge GitHub pull requests after validating status, reviews, and CI results.

Updated Jan 27, 2026
Search Tags:#automation#git#workflow#github#pull-request#merge-pr
One-click install
npx skills add https://github.com/alistairhendersoninfo/ninja_toolbox --skill merge-pr-alistairhendersoninfo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge-pr
Source: https://github.com/alistairhendersoninfo/ninja_toolbox/tree/main/.claude/skills/merge-pr
Command: npx skills add https://github.com/alistairhendersoninfo/ninja_toolbox --skill merge-pr-alistairhendersoninfo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merges GitHub pull requests efficiently by validating status, handling conflicts, and applying the selected merge strategy, reducing manual overhead and human error.

Core Features & Use Cases

  • Validate PR status (open, reviews, CI) before merging.
  • Resolve simple conflicts or alert when manual intervention is required.
  • Apply a chosen merge strategy (squash, merge commit, or rebase) and perform post-merge cleanup.
  • Automate common workflows in collaborative projects with CI pipelines and protected branches.

Quick Start

Provide the PR number and the preferred merge strategy to execute the automated merge workflow.

Frequently Asked Questions about merge-pr

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

FAQPage Schema
How do I automate a GitHub pull request merge with CI checks?▼

You can automate a GitHub pull request merge by providing the PR number and preferred merge strategy to validate status, handle conflicts, and apply the selected merge method.

What is the best way to handle draft status and conflicts before merging a pull request?▼

Handling draft status and conflicts before merging requires a workflow that detects draft PRs, validates reviews, alerts for manual intervention on complex conflicts, or resolves simple conflicts automatically.

Can I choose between squash, merge commit, and rebase strategies for automated PR merges?▼

Yes, you can select squash, merge commit, or rebase as your preferred merge strategy, allowing the automated workflow to apply the chosen method and perform post-merge branch cleanup.

Does automated PR merging work with protected branches and CI pipelines?▼

Automated PR merging works with protected branches and CI pipelines by enforcing a workflow that validates open status, checks review approvals, and verifies CI results before performing the merge.

Why does an automated pull request merge fail on unresolved conflicts?▼

An automated pull request merge fails on unresolved conflicts because the workflow detects conflicting code and alerts for manual intervention rather than forcing a flawed merge.

Related Skills

Explore More Software Engineering Skills→
chf3198chf3198

github-review-merge-admin

Validate GitHub pull request approvals, status checks, and merge readiness.

Community
Intermediate
wsxwj123wsxwj123
7

finishing-a-development-branch

Coordinate merge, PR, or cleanup decisions after tests pass.

Community
Intermediate
aidankinzettaidankinzett
41

github-pr-review

Automate GitHub PR reviews via gh CLI with pending-review workflows.

Community
Advanced
kaiohenricunhakaiohenricunha

review-pr

Automate GitHub pull request review, fix application, and validation workflows.

Community
Advanced