Use when pulling/syncing/updating/absorbing changes from a branch's parent (typically main) into the current branch, or cascading parent changes through a…
inherit Mental model: "I am the child. I want what my parent has." Brings the current branch (and optionally its descendants) up to date with its parent. Inbound counterpart to /ship (outbound to a target) and /isolate (forks a new child from a parent). When to use Current branch is stale relative to its base. A stack of dependent branches needs the parent's latest commits cascaded down. Web sessions or minimal environments where wt, git-trim, gh aren't available. Do NOT use to send changes upward — that's /ship. Do NOT use to create a new branch — that's /isolate. Why merge, not rebase Autonomous mode's git-rewrite-guard.sh blocks git rebase, --amend, reset --hard, and push --force*. Merge is also the parallel-worktree community standard for syncing from base — non-destructive, composes with stacks, never requires a force-push, safe under shared checkouts. Always git merge, never git rebase in this skill. Constraints
don't have the plugin yet? install it then click "run inline in claude" again.