Merge Sprint

Merge related GitHub PRs into a target branch in dependency order.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/AlastairThomson/AgentSkills --skill merge-sprint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Merge Sprint
Source: https://github.com/AlastairThomson/AgentSkills/tree/main/skills/global-scope/merge-sprint
Command: npx skills add https://github.com/AlastairThomson/AgentSkills --skill merge-sprint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merge a batch of related PRs into the target branch in dependency order, resolve conflicts, verify the build after each merge, and clean up leftover worktrees.

Core Features & Use Cases

  • Inventory PRs and determine an independent merge sequence based on file overlaps.
  • Merge PRs one by one with per-PR preflight checks and automatic conflict handling.
  • Clean up temporary worktrees after all merges complete.

Quick Start

Provide a list of PR numbers or a target branch, and the skill will merge them in dependency order with per-PR preflight checks.

Frequently Asked Questions about Merge Sprint

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

FAQPage Schema
How do I merge multiple pull requests in dependency order?

To merge pull requests in dependency order, you provide a list of PR numbers to the skill, which inventories file overlaps to determine a safe sequence and merges them one by one. It automates staged integration for related changes.

Do I need GitHub CLI and git to batch merge pull requests?

Yes, you need GitHub CLI and git installed to batch merge pull requests. The skill relies on these tools to detect conflicts, manage branch integration, and clean up temporary worktrees after the merges complete.

How does conflict resolution work when merging multiple feature branches?

Conflict resolution when merging multiple feature branches is handled with per-PR preflight checks. The skill detects file overlaps automatically and manages conflict handling during the staged merge sequence to ensure safe integration.

Can I verify CI builds after each pull request merge?

Yes, you can verify CI builds after each pull request merge. The skill validates the build after every individual PR integration, ensuring that each staged merge does not break the target branch.

What is the best way to merge sprint PRs safely into a target branch?

The best way to merge sprint PRs safely is to automate the batch process in dependency order. This approach performs per-PR preflight checks, resolves conflicts, and cleans up leftover worktrees for reliable staged integration.