Claude Skill MartBrowse skillsQuick linesLearn by videoTerminal guideWhat is a Skill?
Back to list

Git Master

A rule-driven Git agent that splits work into atomic commits, performs safe rebases/squashes, and digs through history.

Dev & CodingIntermediate67,5315,507AI score 10/10Last updated: Aug 9, 2026

What it does

  • Mode detection: parses your request and routes to COMMIT, REBASE (rebase/squash) or HISTORY_SEARCH.
  • Atomic commit planning: gathers git status, git diff --stat and the last 30 log entries in parallel, detects the repo's commit style (SEMANTIC / PLAIN / SENTENCE / SHORT) and dominant message language, then splits changed files into multiple commits by directory, concern and dependency level. A blocking "COMMIT PLAN" is printed before anything is executed.
  • Safe history rewriting: never rebases main/master, stashes a dirty working tree, insists on --force-with-lease, and includes conflict-resolution plus git reflog / git fsck recovery paths.
  • History archaeology: picks the right tool per question — git log -S (pickaxe), git log -G (regex), git blame -L/-C, git bisect run, git log --follow — and reports results in a compact table with follow-up actions.

Who it's for

  • Developers who tend to dump everything into one giant commit and want review-friendly history
  • Anyone who googles rebase/squash flags every single time
  • Maintainers who often need to answer "who wrote this line / when did this bug appear?"
  • Teams that want commit-convention and message-language consistency enforced automatically

Examples

  1. You changed 8 files and say "commit this" → the skill prints its style-detection result and a 5-commit plan (app layer / demo components / pricing / e2e tests / i18n), then commits in dependency order.
  2. "Clean up this branch and rebase onto main" → safety assessment → stash → autosquash or rebase --onto → guidance for git push --force-with-lease.
  3. "When was the MAX_RETRY_COUNT constant removed?" → runs git log -S "MAX_RETRY_COUNT" --all --oneline and reports the commit hash, author, date and diff excerpt.

· · · Install guide · · ·

Try it now, no install

Paste this into Claude to use the skill without installing anything.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/code-yeongyu/oh-my-openagent/HEAD/packages/skills-loader-core/src/features/builtin-skills/git-master/SKILL.md

What I want: (describe your task here)

If Claude can't open the link, open it yourself and paste the contents instead.

If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.

Install in the Claude app (no terminal)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. 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/skills-loader-core/src/features/builtin-skills/git-master folder from the GitHub repo code-yeongyu/oh-my-openagent into my ~/.claude/skills/code-yeongyu-git-master-2/.
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 && mkdir -p ~/.claude/skills && cp -r oh-my-openagent/packages/skills-loader-core/src/features/builtin-skills/git-master ~/.claude/skills/

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

  1. Open a terminal and go to a working folder.
  2. Clone the repo: git clone https://github.com/code-yeongyu/oh-my-openagent.git
  3. Create the skills folder if needed: mkdir -p ~/.claude/skills
  4. Copy the skill: cp -r oh-my-openagent/packages/skills-loader-core/src/features/builtin-skills/git-master ~/.claude/skills/
  5. Verify it exists: ls ~/.claude/skills/git-master/SKILL.md
  6. Restart Claude Code, open a git repository, and try "commit my changes" or "who wrote this function?".
  7. For your first run, use a disposable branch and read the printed COMMIT PLAN before approving execution.
View source on GitHubLicense: NOASSERTION