git-master
MUST USE whenever a task needs a commit or git-history investigation. Covers atomic commits, staging, commit-message style, rebase, squash, fixup/autosquash, blame, bisect, reflog, git log -S/-G, and questions like who wrote this or when was this added. Do not use for ordinary code edits unless the user asks for git work.
Profile →npx skills add code-yeongyu/oh-my-openagent --skill git-master --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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. Nev
- Mode Gate
- Ground Truth
- PR Body Evidence Attachments
- Commit Mode
- Rebase Mode
- History Mode
- Safety Checks
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/masterWhat does the git-master skill do?
MUST USE whenever a task needs a commit or git-history investigation. Covers atomic commits, staging, commit-message style, rebase, squash, fixup/autosquash, blame, bisect, reflog, git log -S/-G, and questions like who wrote this or when was this added. Do not use for ordinary code edits unless the user asks for git work.
How do I install it?
Run `npx skills add code-yeongyu/oh-my-openagent --skill git-master --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From code-yeongyu/oh-my-openagent, a repository with 67,209 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.