branch-workflowlisted

# Branch Workflow ## Core Question What branch action is safe given the current working tree, tracking configuration, upstream state, divergence, operation state, and requested blast radius? ## When To Use Use this skill when the user asks to: - inspect branch state, - create or switch branches, - sync with upstream, - fetch remote state, - set upstream tracking, - prepare a branch for PR, - push a branch after explicit request, - evaluate force-push or remote branch deletion risk. ## When Not To Use Do not use this skill to resolve file conflicts, recover discarded work, create commits, version a release, or create tags. Route to: - `resolve-conflicts` when unmerged paths or conflict markers exist. - `undo-recover` for reset, restore, abort, reflog, clean, force-push recovery, or destructive recovery. - `atomic-commits` when organizing staged changes into commits. - `tag-release` for Git release tags. - `version-bump`, `release-notes`, or `changelog-maintenance` for release artifacts. ## Required Evidence Before mutation, inspect or establish: - `git status --short --branch`, - current branch name, - branch tracking with `git branch -vv`, - remote names and URLs when remote action is requested, - upstream ref when configured, - ahead/behind counts when upstream exists, - operation state such as merge, rebase, cherry-pick, or revert in progress, - default branch from repository evidence, never assumption, - local and remote SHAs before R4/R5 actions. ## Operating