github

Merge stacked GitHub pull requests using the gh CLI.

Updated Jan 17, 2026

Search Tags:#automation #git #code review #pull request #github #branching

Ready to run

npx skills add https://github.com/epiphanyapps/mapyourhealth --skill github-epiphanyapps

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github
Source: https://github.com/epiphanyapps/mapyourhealth/tree/main/apps/mobile/.agents/skills/github
Command: npx skills add https://github.com/epiphanyapps/mapyourhealth --skill github-epiphanyapps

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates complex GitHub operations, including managing pull requests, implementing branching strategies, and streamlining code review processes.

Core Features & Use Cases

Stacked PR Merging: Merges chains of stacked pull requests cleanly into the main branch using squash commits.
Repository Automation: Leverages the gh CLI for efficient GitHub interactions.
Use Case: When you have a series of dependent pull requests, this skill helps merge them in order, ensuring a clean and manageable Git history.

Quick Start

Use the github skill to merge stacked PRs.

Frequently Asked Questions about github

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

FAQPage Schema

How do I merge stacked pull requests cleanly into the main branch?▼

You can merge stacked pull requests cleanly by automating their sequential merge using squash commits. This approach ensures a clean and manageable Git history during code integration workflows.

What is the best way to automate GitHub pull request management for branching strategies?▼

Automating GitHub pull request management for branching strategies is best handled by leveraging the gh CLI. This streamlines complex repository operations and maintains clean Git history for efficient code review processes.

Do I need the gh CLI installed to manage stacked pull requests?▼

Yes, you need the gh CLI installed and authenticated. Managing stacked pull requests and executing repository automation requires gh CLI installation to perform repository operations and streamline code integration workflows.

Can I use this approach to maintain a clean Git history with dependent code reviews?▼

Yes, you can maintain a clean Git history with dependent code reviews by merging chains of stacked pull requests in order. This ensures efficient code integration workflows without messy commit logs.

Why does managing stacked pull requests manually result in complex Git history?▼

Managing stacked pull requests manually results in complex Git history because dependent changes often create tangled commit logs. Automating the merge process with squash commits resolves this by ensuring a clean integration workflow.