do:merge

Retry deferred Git worktree merges into the main branch.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/adamfeldman/compound-workflows --skill do-merge
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: do:merge
Source: https://github.com/adamfeldman/compound-workflows/tree/main/plugins/compound-workflows/skills/do-merge
Command: npx skills add https://github.com/adamfeldman/compound-workflows --skill do-merge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps resolve issues where a worktree merge into the main branch failed, allowing you to retry the merge process and clean up unmerged branches.

Core Features & Use Cases

  • Automated Merge Detection: Identifies unmerged Git worktrees associated with your session.
  • Intelligent Branch Selection: Automatically selects the branch to merge if only one is found, or prompts you for selection if multiple exist.
  • Conflict Resolution Assistance: Provides options to handle merge conflicts, including automatic resolution for additive changes and user-guided review.
  • Use Case: After a session compaction, you find that a worktree merge to main didn't complete due to conflicts. Running /do:merge will help you resolve these conflicts and finalize the merge.

Quick Start

Run the do:merge skill to merge any unmerged worktree branches into main.

Frequently Asked Questions about do:merge

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

FAQPage Schema
How do I retry a failed git worktree merge into the main branch?▼

To retry a failed git worktree merge, you can run a recovery process that detects unmerged session worktrees, verifies the repository state, and re-executes the merge with conflict handling to finalize the branch integration.

How does conflict resolution work for unmerged worktree branches?▼

Conflict resolution for unmerged worktree branches provides options for automatic resolution of additive changes and user-guided review, ensuring robust handling when retry exhaustion or a dirty main branch occurs during the merge.

What happens when multiple unmerged git worktrees are detected during session recovery?▼

When multiple unmerged git worktrees are detected during session recovery, the process prompts you for manual branch selection, whereas a single unmerged branch is automatically selected for the merge retry.

Can I recover a worktree merge that failed during session compaction?▼

Yes, you can recover a worktree merge that failed during session compaction by identifying the specific unmerged session worktree and executing a targeted merge script to resolve the deferred integration.

What are the limitations when retrying a merge with a dirty main branch?▼

When retrying a merge with a dirty main branch, the process includes robust handling to verify the repository state first, preventing unsafe merges and managing retry exhaustion if conflicts cannot be automatically resolved.