Manage Git State

Establish the requested state change and its authorization. Inspect HEAD, branch/worktrees, index, worktree, and any in-progress operation. Distinguish committed objects from staged blobs and unsaved file contents.

• Read local feedback before code commits, commit-producing integrations, or pushes. Honor existing hooks and repository policy; do not install a hook manager unless that work is requested.
• Read snapshots and refs for scoped commits, partial staging, branch/tag identity, and remote ref updates.
• Read integration and recovery for merge/rebase/cherry-pick, stash/worktree ownership, restore/reset/revert, and reflog recovery.

Preserve unrelated work and configured checks. A ref protects commits, not dirty files. Before an authorized rewrite, retain the original committed and dirty state separately. Prefer the narrow Git operation that produces the requested result; do not turn an ordinary commit into branch restructuring or publication.