merge-concurrent-sprints

Audit Git branches and merge diverged feature branches with conflict resolution.

Updated Dec 8, 2025
One-click install
npx skills add https://github.com/marcusglee11/LifeOS --skill merge-concurrent-sprints
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: merge-concurrent-sprints
Source: https://github.com/marcusglee11/LifeOS/tree/main/.claude/skills/lifeos-workflow/skills/merge-concurrent-sprints
Command: npx skills add https://github.com/marcusglee11/LifeOS --skill merge-concurrent-sprints

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill tackles the challenge of merging multiple feature branches that have diverged significantly, preventing lost work and resolving complex conflicts.

Core Features & Use Cases

  • Branch Auditing: Provides scripts to analyze branch status, commit history, and stash inventory.
  • Merge Strategy Selection: Guides users through choosing the right merge approach (Sequential, Integration Branch, Cherry-Pick) based on branch relationships.
  • Conflict Resolution: Offers systematic steps for handling merge conflicts and ensuring code quality.
  • Use Case: When a team has been working on several features in parallel for over a week, and the main branch has moved on, this skill helps to safely integrate all that work back without breaking the build or losing any commits.

Quick Start

Run the branch audit script to understand the current state of your Git branches before proceeding with any merges.

Frequently Asked Questions about merge-concurrent-sprints

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

FAQPage Schema
How do I merge multiple Git branches that have diverged significantly without losing commits?

To merge multiple diverged Git branches safely, you need a structured workflow that includes pre-merge auditing, selecting an appropriate merge strategy, and systematic conflict resolution. This prevents lost work when integrating parallel features.

What is the best way to merge 5 or more unmerged feature branches in Git?

The best way to merge 5 or more unmerged branches is to first audit branch statuses and commit histories, then choose a merge strategy like sequential merging, an integration branch, or cherry-picking based on branch relationships.

How do I resolve Git merge conflicts when integrating several concurrent feature branches?

Resving Git merge conflicts during concurrent integration requires systematic conflict resolution steps during the merge execution, followed by post-merge cleanup to ensure code quality and prevent build breaks.

When should I use an integration branch versus cherry-picking for complex Git merges?

Use an integration branch for merging multiple parallel features, and cherry-picking for applying specific commits. Branch auditing helps determine the right strategy by clarifying the relationships and divergence between branches.

How do I audit my Git branches and stashes before starting a complex merge?

Auditing Git branches before a merge involves running scripts to analyze branch status, commit history, and stash inventory, providing a clear picture of unmerged branches to ensure safe code integration.