git-master

# Git Master Use this skill when the user asks you to operate on Git history or answer a Git-history question. Be exact, conservative, and evidence-led. Read the repository state before you infer anything. ## Mode Gate Classify the request first: - `COMMIT`: stage and commit local changes. - `REBASE`: rebase, squash, fixup, autosquash, reorder, split, or otherwise rewrite branch history. - `HISTORY`: answer when, where, who, why, or which commit changed something. - `STATUS`: inspect branch, diff, or working-tree state without changing it. Do not commit, rebase, push, force-push, reset, stash-pop, or delete anything unless the user explicitly asked for that operation. If the request is only investigative, report findings and stop. ## Ground Truth Gather independent facts in parallel when the tools allow it: ```bash git status --short git diff --stat git diff --staged --stat git branch --show-current git log -30 --oneline git log -30 --pretty=format:%s git rev-parse --abbrev-ref @{upstream} git merge-base HEAD origin/main git merge-base HEAD origin/master ``` Missing upstream or missing `main`/`master` is normal. Fall back to the best available branch or report the missing fact. Never treat a failed lookup as proof. ## PR Body Evidence Attachments When a PR body needs screenshots or terminal PNGs, use the repo reference at `docs/reference/github-attachment-upload.md`. The allowed hosting path is GitHub user attachments from the authenticated web attachment flow; nev...