repo-state-diagnosislisted

# Repo State Diagnosis ## Core Question What is the current repository state, and which skill should own the next safe action? ## When To Use Use this skill when: - the user asks what state the repo or branch is in - another skill needs read-only orientation before mutation - the repository may be dirty, conflicted, detached, diverged, missing upstream, or in an operation state - the correct Git skill is unclear ## When Not To Use Do not use this skill when: - executing branch sync, commit, recovery, or conflict resolution - creating commits or tags - running destructive cleanup - publishing or pushing remote refs Route to: - commit planning routes to `atomic-commits` - message-only work routes to `conventional-commits` - branch update or upstream work routes to `sync-branch` or `branch-workflow` - conflicts route to `resolve-conflicts` - abort/recovery routes to `undo-recover` ## Required Evidence Before action, inspect or establish: - `git status --short --branch` - current branch and HEAD mode - staged, unstaged, and untracked path groups - upstream, ahead, and behind state - operation state markers for merge, rebase, cherry-pick, and revert - recent log or graph only when needed for state explanation 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 Cont