merge-pr

Merge GitHub pull requests with the gh CLI after validating CI checks and approvals.

2|Updated Aug 16, 2011
One-click install
npx skills add https://github.com/sakuro/dotfiles --skill merge-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: merge-pr
Source: https://github.com/sakuro/dotfiles/tree/main/.config/claude/skills/merge-pr
Command: npx skills add https://github.com/sakuro/dotfiles --skill merge-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires github-cli.

What problem does it solve?

This Skill streamlines the process of merging GitHub Pull Requests, ensuring all pre-merge checks are passed and project conventions are followed. It reduces errors, manual oversight, and the cognitive load of managing complex merge workflows.

Core Features & Use Cases

  • Pre-Merge Validation: Automatically checks CI status, required approvals, and unresolved review comments before merging.
  • Merge Strategy Guidance: Recommends and executes appropriate merge strategies (merge commit, squash, rebase) with proper commit message formatting.
  • Post-Merge Cleanup: Guides on updating local branches and cleaning up merged branches to keep your local repository tidy.
  • Use Case: A team lead needs to merge several pull requests but wants to ensure all CI checks pass, required approvals are met, and the merge commit message follows conventions. This skill automates the verification and merging process, providing a consistent and safe workflow.

Quick Start

Use the merge-pr skill to merge pull request #123, ensuring all checks pass and using the default merge commit strategy.

Frequently Asked Questions about merge-pr

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

FAQPage Schema
How do I merge a pull request safely with CI checks and approvals?

Merge pull requests safely by validating CI status and required approvals before merging. This Skill automatically checks that all CI checks pass and required reviewers have approved before executing the merge, ensuring your code meets project standards.

What merge strategies does the gh CLI support?

The gh CLI supports three merge strategies: merge commit, squash, and rebase. This Skill guides you to select the appropriate strategy for your workflow and ensures the merge commit message follows your project's conventions.

Can I automate branch cleanup after merging a pull request?

Yes, this Skill respects repository settings for automatic branch deletion after merge and guides you on updating your local repository afterward. It handles post-merge cleanup to keep your local branches synchronized.

How do I validate unresolved review comments before merging?

This Skill performs pre-merge validation that includes checking for unresolved review comments alongside CI status and approvals. It prevents merging until all blocking issues are resolved, reducing manual oversight.

Does this work with GitHub's branch protection rules?

Yes, this Skill integrates with GitHub's branch protection requirements including required approvals and status checks. It validates these rules before merging to ensure compliance with your repository's protection policies.

Related Skills