skills.rest
FutureAtoms
FutureAtomsCOMMUNITY
Explore all skills by this author →
GitHub

git-github-merge-pr

Merge GitHub pull requests with pre-merge validation and gh CLI commands.

1|Updated Mar 11, 2026
Search Tags:#git#ci/cd#code review#version control#pull request#github#merge
One-click install
npx skills add https://github.com/FutureAtoms/claude-skills-backup --skill git-github-merge-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-github-merge-pr
Source: https://github.com/FutureAtoms/claude-skills-backup/tree/main/git-github-merge-pr
Command: npx skills add https://github.com/FutureAtoms/claude-skills-backup --skill git-github-merge-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of merging pull requests by providing a structured approach to validation, method selection, and post-merge cleanup, ensuring code quality and maintainable history.

Core Features & Use Cases

  • Pre-Merge Checklist: Guides users through essential checks like CI status, approvals, and conflict resolution.
  • Merge Method Selection: Explains and facilitates Merge Commit, Squash, and Rebase strategies based on project needs.
  • Automated Commands: Provides gh CLI commands for merging, updating branches, and managing PRs.
  • Use Case: A developer needs to merge a feature branch into main. This Skill helps them verify all checks are green, choose the best merge strategy (e.g., squash for a clean history), execute the merge command, and clean up the feature branch afterward.

Quick Start

Use the git-github-merge-pr skill to merge pull request number 123 using a squash merge and delete the branch.

Frequently Asked Questions about git-github-merge-pr

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

FAQPage Schema
How do I safely merge a GitHub pull request using the command line?▼

To safely merge a GitHub pull request, validate CI status and approvals, select an appropriate merge method, execute GitHub CLI commands for merging, and clean up the feature branch afterward.

What is the difference between merge commit, squash, and rebase when merging a PR?▼

Merge commit preserves complete history, squash combines commits into a single commit for a clean log, and rebase applies commits sequentially to maintain a linear project history.

How do I verify CI checks and branch protection rules before merging a pull request?▼

Verify CI checks and branch protection rules before merging by running a pre-merge checklist that confirms CI status is green, required approvals are met, and merge conflicts are resolved.

Can I use the GitHub CLI to delete a feature branch after merging a pull request?▼

Yes, you can use the GitHub CLI to delete a feature branch after merging a pull request as part of the post-merge cleanup process to maintain a clean repository state.

What is the best way to automate pull request merging with branch protection compliance?▼

The best way to automate pull request merging with branch protection compliance is to use a structured workflow that validates pre-merge checks and executes GitHub CLI commands for the selected merge method.

Related Skills

Explore More Software Engineering Skills→
bkelly-labbkelly-lab
50

approve-pr

Automate GitHub PR pre-flight checks, approval, and squash-merge with branch deletion.

Official
Intermediate
shep-aishep-ai
241

shep-kit:merged

Switch to the main branch, pull updates, and delete the merged feature branch.

Official
Intermediate
a-taka-tak
1

git-create-pr

Commit changes, push to origin, and create a GitHub Pull Request.

Community
Intermediate
zhaow-dezhaow-de

merge-pr

Merge reviewed GitHub pull requests with a merge commit.

Community
Intermediate