From agenthub
Merge the winning agent's branch into base, archive losers, and clean up worktrees.
How this skill is triggered — by the user, by Claude, or both
Slash command
/agenthub:mergeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Merge the best agent's branch into the base branch, archive losing branches via git tags, and clean up worktrees.
Merge the best agent's branch into the base branch, archive losing branches via git tags, and clean up worktrees.
/hub:merge # Merge winner of latest session
/hub:merge 20260317-143022 # Merge winner of specific session
/hub:merge 20260317-143022 --agent agent-2 # Explicitly choose winner
If --agent specified, use that. Otherwise, use the #1 ranked agent from the most recent /hub:eval.
git checkout {base_branch}
git merge --no-ff hub/{session-id}/{winner}/attempt-1 \
-m "hub: merge {winner} from session {session-id}
Task: {task}
Winner: {winner}
Session: {session-id}"
For each non-winning agent:
# Create archive tag (preserves commits forever)
git tag hub/archive/{session-id}/{agent-id} hub/{session-id}/{agent-id}/attempt-1
# Delete branch ref (commits preserved via tag)
git branch -D hub/{session-id}/{agent-id}/attempt-1
python {skill_path}/scripts/session_manager.py --cleanup {session-id}
Write .agenthub/board/results/merge-summary.md:
---
author: coordinator
timestamp: {now}
channel: results
---
## Merge Summary
- **Session**: {session-id}
- **Winner**: {winner}
- **Merged into**: {base_branch}
- **Archived**: {loser-1}, {loser-2}, ...
- **Worktrees cleaned**: {count}
python {skill_path}/scripts/session_manager.py --update {session-id} --state merged
--no-ff for clear historyTell the user:
{base_branch}hub/archive/{session-id}/agent-{N}mergednpx claudepluginhub alexbramall/claude-code-skills --plugin agenthubGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.
4plugins reuse this skill
First indexed May 17, 2026