merge

Merge the winning agent's branch into the base and archive losing branches.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/Patasse97/claude-skills --skill merge-patasse97
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: merge
Source: https://github.com/Patasse97/claude-skills/tree/main/engineering/agenthub/skills/merge
Command: npx skills add https://github.com/Patasse97/claude-skills --skill merge-patasse97

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates coordinating post-session code integration by merging the winning agent's branch into the base and archiving losers to preserve history.

Core Features & Use Cases

  • Identify the winning agent from the latest evaluation and merge its branch into the base.
  • Archive losing branches with tags, preserving history while keeping the main tree clean.
  • Clean up worktrees and update the session state with a post-merge summary.

Quick Start

Run the merge command to apply the winning branch to the base and tidy up the session.

Frequently Asked Questions about merge

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

FAQPage Schema
How do I automate merging the winning branch into the base after a session?

Automate post-session branch merging by running the merge command to integrate the winning agent's branch into the base, tag losing branches for archiving, and clean up worktrees. This unifies results and updates the session state with a post-merge summary.

What is the best way to archive losing git branches while keeping the main tree clean?

Archive losing git branches by tagging them before removal, which preserves their history without cluttering the main tree. The automation workflow handles this by identifying the winner, applying it to the base, and tagging losers during cleanup.

How does post-session worktree cleanup work when integrating multiple agent branches?

Post-session worktree cleanup works by merging the winning agent's branch into the base branch, tagging and archiving the losing branches, and automatically removing leftover worktrees to update the session state with a final summary.

Can I coordinate code integration across multiple git worktrees and sessions automatically?

Yes, you can coordinate code integration across multiple git worktrees and sessions automatically. The workflow applies safe merge practices to unify results, log outcomes, and clean up leftovers across all active worktrees in the session.

Does the merge workflow preserve the history of losing branches after selecting a winner?

Yes, the merge workflow preserves losing branch history by applying tags to archive them before deletion. This ensures the main tree remains clean while keeping the historical commit data of losing agents fully accessible.

What happens to the session state after a branch merge and worktree cleanup?

After a branch merge and worktree cleanup, the session state is automatically updated with a post-merge summary. The workflow logs the results of the safe merge practices to reflect the newly unified base branch and archived losers.