What problem does it solve? Merging parallel worktree branches into a shared default branch often involves manual Git commands, lost history from squash or fast-forward merges, and race conditions when multiple agents merge concurrently. This Skill enforces a verified, atomic two-parent merge through the shared git-discipline executable. ## Core Features & Use Cases - Policy-aware merge targets: Reads the repository's git-discipline mode (local-only, auto-trunk, gated-trunk, pr-flow, external) and selects the correct local or remote merge path. - Candidate verification: Rebases the candidate onto the default tip and runs a test command at the exact candidate SHA before merging. - Atomic compare-and-swap merge: Creates a real two-parent merge commit and updates the default ref with compare-and-swap semantics, retrying on lost races. - Use Case: After finishing a feature in a git worktree, invoke this Skill to verify the candidate with your test suite, merge it into main as a two-parent commit, and hand the worktree to bonsai:prune for cleanup. ## Quick Start Ask the agent to verify and merge the current worktree candidate into the default branch using the git-discipline merge workflow.