How do I install the Pr Merge Temporal skill?

Run npx skillmds@latest add majiayu000/pr-merge-temporal 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 Temporal 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 Temporal?

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 Temporal free to use?

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

Who published Pr Merge Temporal?

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

Pr Merge Temporal by majiayu000 — Agent Skill

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

Pr Merge Temporal

Merge multiple PRs into a temporal integration branch before merging to base, with ordered conflict resolution. Use when you want to validate a set of PRs together on a staging branch before advancing the base branch.

majiayu000 Updated Sep 9, 2026 567 repo stars

File contents

Smart Merge to Temporal Branch

Merge multiple PRs into a temporal integration branch for validation before merging to base.

Process

Detect base branch: Identify the default branch via git remote show origin or repo conventions.
Enumerate PRs: List all PRs to merge. For each, fetch the latest HEAD.
Create temporal branch: Fetch latest and branch from the remote base tip.
```
git fetch origin
git checkout -b temporal/<timestamp> origin/<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 temporal branch. b. If merge succeeds cleanly, continue to next PR. c. If conflicts occur:
- Analyze each conflict 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 (git merge --abort), stop, and report the conflict with both sides and a recommended resolution. d. After each successful merge, run available build/test commands to catch regressions early.
Validate temporal branch: Once all PRs are merged, run full build/test suite if available.
Report results: Present the validated temporal branch to the user. Do NOT merge into base automatically — only advance 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. The temporal branch is abandoned: git checkout <base> — base remains untouched.

Output

Report for each PR: merged successfully, conflicts resolved (with details), or blocked (with reason). Include the temporal branch name for user review.

---name: pr-merge-temporaldescription: Merge multiple PRs into a temporal integration branch before merging to base, with ordered conflict resolution. Use when you want to validate a set of PRs together on a staging branch before advancing the base branch.---# Smart Merge to Temporal Branch Merge multiple PRs into a temporal integration branch for validation before merging to base. ## Process 1. **Detect base branch**: Identify the default branch via `git remote show origin` or repo conventions. 2. **Enumerate PRs**: List all PRs to merge. For each, fetch the latest HEAD. 3. **Create temporal branch**: Fetch latest and branch from the remote base tip. ``` git fetch origin git checkout -b temporal/<timestamp> origin/<base> ``` 4. **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. 5. **Sequential merge with conflict handling** — for each PR in order: a. Attempt `git merge --no-ff <pr-branch>` into the temporal branch. b. If merge succeeds cleanly, continue to next PR. c. If conflicts occur: - Analyze each conflict 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 (`git merge --abort`), stop, and report the conflict with both sides and a recommended resolution. d. After each successful merge, run available build/test commands to catch regressions early. 6. **Validate temporal branch**: Once all PRs are merged, run full build/test suite if available. 7. **Report results**: Present the validated temporal branch to the user. Do NOT merge into base automatically — only advance base if the user explicitly requests it. 8. **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. The temporal branch is abandoned: `git checkout <base>` — base remains untouched. ## Output Report for each PR: merged successfully, conflicts resolved (with details), or blocked (with reason). Include the temporal branch name for user review.

Frequently asked questions