pbi-merge

Merge completed Product Backlog Items into the main branch with lock protection.

15|5|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/sohei56/maul-team --skill pbi-merge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pbi-merge
Source: https://github.com/sohei56/maul-team/tree/main/skills/pbi-merge
Command: npx skills add https://github.com/sohei56/maul-team --skill pbi-merge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill safely orchestrates merging a completed Product Backlog Item into the main branch while preventing unsafe parallel merges, preserving repository state, and routing failures to the right recovery path.

Core Features & Use Cases

  • Controlled Merge Execution: Runs the repository's merge wrapper with lock protection and validates backlog, worktree, branch, and tracked-file preconditions.
  • Failure-Aware Recovery: Distinguishes preflight errors, merge conflicts, missing artifacts, regression failures, and post-merge bookkeeping faults using explicit exit codes.
  • Developer Coordination: Sends targeted instructions for conflict resolution, artifact restoration, regression debugging, retries, and escalation after three consecutive failures.
  • Use Case: When a Developer reports that a PBI is ready to merge, use this Skill to merge it, confirm the resulting status, notify the Developer, or initiate the appropriate recovery workflow.

Quick Start

Ask the Skill to process the PBI identified by the Developer's PBI_READY_TO_MERGE notification and complete the merge or recovery workflow.

Frequently Asked Questions about pbi-merge

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

FAQPage Schema
How do I handle a merge conflict when merging a Product Backlog Item into the main branch?

To resolve a PBI merge conflict, the system detects the failure, pauses the merge process, and issues specific resolution instructions to the Developer to fix the conflicting files before proceeding.

What happens if a regression failure occurs after a PBI merge?

If a regression failure occurs post-merge, the workflow isolates the failure, routes the issue for regression debugging, and prevents unsafe parallel merges from corrupting the main branch state.

How do I escalate a PBI merge that keeps failing?

To escalate a repeatedly failing PBI merge, the system tracks consecutive merge failures and automatically triggers an escalation workflow after three unsuccessful attempts to ensure Scrum Master intervention.

Do I need specific shell wrappers to merge a PBI safely?

Yes, safely merging a PBI requires the repository's merge and bookkeeping shell wrappers, valid Scrum state files, and strict protection against direct branch operations to ensure serialized processing.

What is the best way to prevent unsafe parallel merges in a Scrum workflow?

The best way to prevent unsafe parallel merges is to use lock protection and serialized processing within a controlled merge execution wrapper that validates backlog, worktree, and branch preconditions.

Why does a PBI merge fail with missing artifacts?

A PBI merge fails with missing artifacts because the preflight validation checks detect incomplete required deliverables, triggering a failure-aware recovery path that requests artifact restoration from the Developer.