Diagnose Repository State

Objective

Build a precise, non-mutating explanation of the repository's current state and route the user to the smallest next workflow.

Use When

• Git reports an unfamiliar state or error and the user does not know what to do next.
• Status and diff appear inconsistent, or a file seems changed, ignored, missing, or untracked.
• HEAD is detached, unborn, missing, or an operation such as merge/rebase/cherry-pick is in progress.
• Repository integrity, shallow-clone, alternates, linked-worktree, or object-availability concerns must be diagnosed.

Do Not Use / Route Elsewhere