skills.rest
wutongshenqiu
wutongshenqiuCOMMUNITY
Explore all skills by this author →
GitHub

merge

Merge pull requests in a user-defined order with rebase conflict handling.

Updated Feb 27, 2026
Search Tags:#dependency management#GitHub#code integration#batch merge#PR merging
One-click install
npx skills add https://github.com/wutongshenqiu/prism --skill merge-wutongshenqiu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge
Source: https://github.com/wutongshenqiu/prism/tree/main/.agents/skills/merge
Command: npx skills add https://github.com/wutongshenqiu/prism --skill merge-wutongshenqiu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, and includes scripts (resource) components.

What problem does it solve?

Manages the merging of multiple pull requests (PRs) in a specified order, handling conflicts and dependencies efficiently.

Core Features & Use Cases

  • Sequential Merging: Merges PRs in a user-defined order to ensure dependency resolution.
  • Conflict Handling: Resolves conflicts by pulling, rebasing, and pushing with caution.
  • Dependency Management: Ensures that dependent PRs are merged after their base PRs.
  • Use Case: Ideal for merging a series of related PRs that must be applied in a specific sequence, ensuring code integrity and minimizing merge conflicts.

Quick Start

Use the merge skill to combine the following PRs in sequence: merge 81 85 86.

Frequently Asked Questions about merge

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

FAQPage Schema
How do I batch merge multiple GitHub pull requests in a specific order?▼

To batch merge multiple GitHub pull requests in a specific order, you can specify PR numbers sequentially, such as `merge 81 85 86`. This skill manages the merge sequence automatically, pulling, rebasing, and force-pushing to resolve conflicts while ensuring dependent PRs merge after their base PRs.

What is the best way to handle merge conflicts when combining related pull requests?▼

Handling merge conflicts when combining related pull requests is done by rebasing and force-pushing. This approach resolves conflicts during the sequential merge process, maintaining code integrity across dependent PRs without manual intervention.

Do I need git and GitHub API access to automate batch PR merging?▼

Yes, you need git and GitHub API access to automate batch PR merging, as the process relies on gh and git commands. These dependencies are required to manage the repository, execute rebases, and push the resolved code integration.

Can I ensure dependent PRs are merged after their base PRs automatically?▼

You can ensure dependent PRs are merged after their base PRs automatically through dependency management. This skill tracks the user-defined merge order, guaranteeing that prerequisite base PRs are successfully integrated before any dependent pull requests are processed.

What are the limitations of using scripts for sequential PR merging?▼

Limitations of using scripts for sequential PR merging include potential failures during complex conflict resolution that cannot be automatically rebased. The process focuses on dependency management and sequential integration, so unresolvable code conflicts may require manual intervention before continuing.

Related Skills

Explore More Software Engineering Skills→
granietgraniet
247

github-auth

Automates GitHub authentication setup for git, SSH, gh CLI, and API access.

Community
Intermediate
esopianesopian
2

land-and-deploy

Merges pull requests, waits for CI completion, deploys to production, and verifies health via canary tests.

Community
Advanced
patricio0312revpatricio0312rev
5

quality-gates-enforcer

Enforce CI quality gates for coverage, linting, type checks, and security in Node.js PR workflows.

Community
Advanced
paultyngpaultyng
9

rebase-pr-chain

Rebase stacked GitHub pull requests in dependency order and verify mergeability.

Community
Intermediate