ghs-merge-prs

Merge open GitHub pull requests with CI status awareness and branch cleanup.

2|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/Atypical-Consulting/GitHubSkills --skill ghs-merge-prs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ghs-merge-prs
Source: https://github.com/Atypical-Consulting/GitHubSkills/tree/main/.claude/skills/ghs-merge-prs
Command: npx skills add https://github.com/Atypical-Consulting/GitHubSkills --skill ghs-merge-prs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of merging pull requests in GitHub repositories, ensuring that only eligible and properly checked code is merged into the main branch.

Core Features & Use Cases

  • Batch Merging: Merge multiple PRs at once, including bot-generated PRs (e.g., Renovate, Dependabot) and your own PRs.
  • CI Awareness: Intelligently handles PRs based on their CI status, warning or skipping PRs with failing checks.
  • Branch Cleanup: Automatically deletes merged branches to keep the repository tidy.
  • Use Case: You have several dependency update PRs from Renovate that have passed CI. Use this Skill to merge them all with a single command, keeping your dependencies up-to-date.

Quick Start

Use the ghs-merge-prs skill to merge all renovate PRs in the current repository.

Frequently Asked Questions about ghs-merge-prs

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

FAQPage Schema
How do I merge multiple pull requests on GitHub at the same time?

You can merge multiple pull requests at once by using batch operations that group bot PRs, user PRs, or all eligible PRs together. This allows you to process several dependency updates or feature branches with a single command.

Can I automatically merge Renovate and Dependabot PRs in batch?

Yes, batch merging specifically supports bot-generated PRs from tools like Renovate and Dependabot. You can merge all passing dependency update PRs in your repository simultaneously to keep your dependencies current.

Does merging pull requests check CI status before completing the merge?

Yes, this approach is CI-aware and intelligently handles PRs based on their CI status. It will warn you about or skip pull requests that have failing checks to ensure only properly verified code is merged.

Do I need the GitHub CLI to merge pull requests with branch cleanup?

Yes, you need the GitHub CLI installed for authenticated API interactions. It provides the necessary network access to execute merges and automatically delete merged branches to keep your repository tidy.

What is the best way to handle branch cleanup after merging multiple PRs?

Automatic branch cleanup deletes merged branches immediately after the pull request is completed. This keeps your repository tidy without requiring manual deletion of stale branches after batch merging.

When should I use squash merge instead of a regular merge for pull requests?

The merge strategy applies squash or regular merges based on the PR author and your preference. Squash merges are typically used for bot PRs to maintain a clean history, while regular merges can be applied to user-authored PRs.