Git Master

An expert Git agent that splits work into atomic commits, cleans history with rebase/squash, and digs through history to find when and why code changed.

Dev & CodingIntermediate★ 67,531⑂ 5,507AI score 8/10Last updated: Aug 9, 2026

What it does

The skill detects your intent (in any language) and switches into one of three modes.

COMMIT mode: gathers git status, git diff, and git log -30 in parallel, detects the repo's existing commit style (semantic / plain / sentence / short) and dominant language, then groups changed files by directory, concern, and dependency level into multiple atomic commits. Tests stay with their implementation, and the skill must print a commit plan with per-group justification before executing anything.
REBASE mode: runs a safety assessment (on main? pushed? dirty tree?) and then performs interactive squash, autosquash of fixup! commits, rebase --onto, reorder, or commit splitting — including conflict-resolution steps and recovery via git reflog and --force-with-lease.
HISTORY SEARCH mode: maps questions like "when was X added", "who wrote this line", or "when did this bug start" to git log -S (pickaxe), git log -G, git blame -L/-C, and git bisect run, then formats the findings into a readable report with follow-up actions.

Who it's for

Developers who habitually dump everything into one giant commit
Anyone who avoids rebase/squash and lets branch history get messy
Maintainers of legacy code who frequently need to trace the origin of a change
Teams that want commit messages to automatically match the repo's existing convention

Examples

Cleaning up a large change: after editing 8 files you say "commit this" — the skill prints a 5-commit plan (app layer / demo components / pricing / e2e tests / i18n) with justifications, then commits in dependency order.
Pre-PR history cleanup: "squash the fixups on this branch" — it finds the merge-base, runs GIT_SEQUENCE_EDITOR=: git rebase -i --autosquash, and warns you that git push --force-with-lease is required.
Bug archaeology: "when was MAX_RETRY_COUNT removed?" — it runs git log -S "MAX_RETRY_COUNT" --all --oneline, reports the culprit commit with author, date, and a diff excerpt, and suggests git show / git revert follow-ups.

· · · Install guide · · ·

Install in the Claude app (no terminal)

Download the ZIP with the button below.
In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.

↓ Download ZIP

Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the packages/omo-opencode/src/features/builtin-skills/git-master folder from the GitHub repo code-yeongyu/oh-my-openagent into my ~/.claude/skills/git-master/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/code-yeongyu/oh-my-openagent.git /tmp/oh-my-openagent && mkdir -p ~/.claude/skills/git-master && cp /tmp/oh-my-openagent/packages/omo-opencode/src/features/builtin-skills/git-master/SKILL.md ~/.claude/skills/git-master/

⚠ This is a third-party skill. Check the source repository before installing.

Open a terminal and move to a temporary working directory.
Clone the repository: git clone https://github.com/code-yeongyu/oh-my-openagent.git
Create the skill folder: mkdir -p ~/.claude/skills/git-master
Copy the skill file: cp oh-my-openagent/packages/omo-opencode/src/features/builtin-skills/git-master/SKILL.md ~/.claude/skills/git-master/
Restart Claude Code and confirm git-master appears in your skills list.
Try it on a scratch branch: ask "commit my changes" or "when was this function added?".
(Recommended) Review the printed commit/rebase plan before approving execution, and avoid running rebase or reset --soft flows directly on shared branches.

View source on GitHub ↗License: NOASSERTION