How do I install the Pr Merge Base skill?

Run npx skillmds@latest add majiayu000/pr-merge-base in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pr Merge Base safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pr Merge Base?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pr Merge Base free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pr Merge Base?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pr Merge Base by majiayu000 — Agent Skill

Name: Pr Merge Base
Rating: 4.2 (5 reviews)
Author: majiayu000

Pr Merge Base

Merge one or more PRs into the base branch with queue-like sequencing and conflict resolution. Use when merging PRs that may conflict with each other or the base, requiring ordered application and intelligent conflict handling.

majiayu000 Updated Sep 9, 2026 567 repo stars

File contents

Smart Merge to Base Branch

Merge one or more PRs into the base branch (main/master) using queue-like sequencing.

Process

Detect base branch: Identify the default branch (main, master, or repo-specific) via git remote show origin or repo conventions.
Enumerate PRs: List all PRs to merge. For each, fetch the latest HEAD.
Create checkpoint: Record the current base branch tip as a rollback point.
```
CHECKPOINT=$(git rev-parse HEAD)
```
Create integration branch: Work on a temporary branch to validate before touching base.
```
git checkout -b merge-queue/<timestamp> <base>
```
Determine merge order:
- If the user specifies an order, use that.
- Otherwise, compute dependency/topological order (if PR B depends on PR A, merge A first).
- If PRs are independent with no clear ordering, present the list and ask the user to confirm or reorder before proceeding.
Sequential merge with conflict handling — for each PR in order: a. Attempt git merge --no-ff <pr-branch> into the integration branch. b. If merge succeeds cleanly, continue to next PR. c. If conflicts occur:
- Analyze each conflict file using difft and codebase context.
- Apply resolution using structural understanding (prefer base for formatting, PR for logic).
- If a conflict cannot be resolved with confidence, abort this merge (git merge --abort), stop and report the conflict to the user with both sides and a recommended resolution. d. After each successful merge, verify the build still passes (if build commands are available).
Validate integration branch: Once all PRs are merged on the integration branch, run full build/test suite if available.
Report results: Present the validated integration branch to the user. Do NOT advance the base branch automatically — only update base if the user explicitly requests it.
Abort conditions — stop the queue and report if:
- A conflict cannot be safely auto-resolved.
- A post-merge build/test fails.
- A PR has been superseded or closed. Roll back: git checkout <base> && git branch -D merge-queue/<timestamp> — base remains untouched at checkpoint.

Output

Report for each PR: merged successfully, conflicts resolved (with details), or blocked (with reason).

---name: pr-merge-basedescription: Merge one or more PRs into the base branch with queue-like sequencing and conflict resolution. Use when merging PRs that may conflict with each other or the base, requiring ordered application and intelligent conflict handling.---# Smart Merge to Base Branch Merge one or more PRs into the base branch (main/master) using queue-like sequencing. ## Process 1. **Detect base branch**: Identify the default branch (`main`, `master`, or repo-specific) via `git remote show origin` or repo conventions. 2. **Enumerate PRs**: List all PRs to merge. For each, fetch the latest HEAD. 3. **Create checkpoint**: Record the current base branch tip as a rollback point. ``` CHECKPOINT=$(git rev-parse HEAD) ``` 4. **Create integration branch**: Work on a temporary branch to validate before touching base. ``` git checkout -b merge-queue/<timestamp> <base> ``` 5. **Determine merge order**: - If the user specifies an order, use that. - Otherwise, compute dependency/topological order (if PR B depends on PR A, merge A first). - If PRs are independent with no clear ordering, present the list and ask the user to confirm or reorder before proceeding. 6. **Sequential merge with conflict handling** — for each PR in order: a. Attempt `git merge --no-ff <pr-branch>` into the integration branch. b. If merge succeeds cleanly, continue to next PR. c. If conflicts occur: - Analyze each conflict file using `difft` and codebase context. - Apply resolution using structural understanding (prefer base for formatting, PR for logic). - If a conflict cannot be resolved with confidence, **abort this merge** (`git merge --abort`), **stop and report** the conflict to the user with both sides and a recommended resolution. d. After each successful merge, verify the build still passes (if build commands are available). 7. **Validate integration branch**: Once all PRs are merged on the integration branch, run full build/test suite if available. 8. **Report results**: Present the validated integration branch to the user. Do NOT advance the base branch automatically — only update base if the user explicitly requests it. 9. **Abort conditions** — stop the queue and report if: - A conflict cannot be safely auto-resolved. - A post-merge build/test fails. - A PR has been superseded or closed. Roll back: `git checkout <base> && git branch -D merge-queue/<timestamp>` — base remains untouched at checkpoint. ## Output Report for each PR: merged successfully, conflicts resolved (with details), or blocked (with reason).

Frequently asked questions