sync-branchlisted

# Sync Branch ## Core Question How should this branch be safely brought up to date while preserving user work and making merge/rebase risk explicit? ## When To Use Use this skill when: - the user asks to pull, fetch, sync, update, rebase onto, or merge from an upstream branch - the branch is behind or diverged - the user wants remote state refreshed - the user asks why pull is blocked or risky ## When Not To Use Do not use this skill when: - general branch creation or deletion - conflict file resolution - abort/reset/recovery - force-push or remote deletion - commit grouping Route to: - branch creation or push gates route to `branch-workflow` - conflicts after sync route to `resolve-conflicts` - abort or recovery routes to `undo-recover` - dirty work that should be committed routes to `atomic-commits` or `stash-shelve` ## Required Evidence Before action, inspect or establish: - current branch, upstream, and target branch - status including staged, unstaged, and untracked paths - ahead/behind/diverged evidence - merge-base and recent log when branch relationship is ambiguous - operation-in-progress markers - project policy for merge versus rebase when available No-evidence rule: - Do not make strong claims without observed evidence. - State assumptions when proceeding under incomplete evidence. - Stop when missing evidence affects safety, correctness, user work, remote state, or irreversible action. ## Operating Contract You MAY: - inspect relevant repository