merge-all

Merge open pull requests into main with automated testing between each merge.

1|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/cwilliams5/Alt-Tabby --skill merge-all
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: merge-all
Source: https://github.com/cwilliams5/Alt-Tabby/tree/main/.claude/skills/merge-all
Command: npx skills add https://github.com/cwilliams5/Alt-Tabby --skill merge-all

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of merging multiple open pull requests into the main branch while ensuring code quality through automated testing between each merge.

Core Features & Use Cases

  • Automated Merging: Merges open pull requests sequentially.
  • Conflict Detection: Stops the process if merge conflicts are detected, preventing broken merges.
  • Integrated Testing: Runs a full test suite after each merge to catch regressions early.
  • Use Case: For a busy open-source project, this skill can be used at the end of the day to merge all approved PRs into the main branch, ensuring that the codebase remains stable and tested.

Quick Start

Use the merge-all skill to merge all open pull requests into the main branch.

Frequently Asked Questions about merge-all

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

FAQPage Schema
How do I automate merging multiple open pull requests into the main branch?

Automating pull request merges involves sequentially merging open PRs into the main branch using GitHub CLI. This Skill handles the entire process by listing PRs, verifying mergeability, and pulling the latest main branch changes automatically.

Can I run a full test suite automatically after each pull request merge?

Running a full test suite after each PR merge is fully supported. The Skill executes your complete test suite after every individual merge operation to detect regressions early before proceeding to the next pull request.

What happens to the automated merge process if a pull request has merge conflicts?

When merge conflicts are detected during the automated process, the Skill halts immediately and reports the specific PR causing the issue. This prevents broken merges from being pushed into the main branch.

Does this automated PR merging tool require any external dependencies to run?

No external dependencies are required for this automated PR merging tool. It operates using internal scripts and leverages the GitHub CLI to handle pull request listing, mergeability checks, and merge operations directly.

How do I clean up local worktrees after merging pull requests in GitHub?

Cleaning up local worktrees after merging pull requests is handled automatically by the Skill. It pulls the latest main branch, completes the testing phase, and then performs local worktree cleanup to free up space.