What tools does it use for history searching?

It acts as a 'History Archaeologist' using advanced commands like git blame, git bisect, and git log -S to find when specific code snippets were added or removed.

How does Git Master prevent large, messy commits?

The skill follows a non-negotiable hard rule for atomic commits: if you change 3+ files, it automatically splits them into multiple commits based on directory, module, and logical concern.

Is it safe to use for history rewriting and rebasing?

Git Master includes a mandatory branch analysis phase. It checks if your commits are pushed or local-only and warns you before performing force-pushes or aggressive rewrites.

Can it adapt to my team's specific commit message format?

Yes. Before committing, it analyzes the last 30 commits to detect if your style is Semantic, Plain, Sentence, or Short, and matches the primary language (English or Korean) used in the repo.

Git Master Agent

Name: Git Master Agent
Author: robertpelloni

byrobertpelloni

•

Developer Tools

Enforces atomic commit standards and automates complex git workflows including rebasing and history analysis.

About

The Git Master Agent is a specialized Claude Code skill designed for developers who demand high-quality version control. It functions as a Commit Architect, Rebase Surgeon, and History Archaeologist all in one. The skill prevents messy 'mega-commits' by strictly enforcing atomic unit planning—splitting changes by module, concern, and directory. It automatically adapts to your project's specific conventions by analyzing recent history for language (English/Korean) and style (Semantic, Plain, Sentence, or Short), ensuring every commit feels native to your repository. Whether you are cleaning up a feature branch or hunting down a regression with git bisect, this skill provides the expertise to maintain a professional and readable project history.

Key Features

Strict atomic commit enforcement based on file count and logical boundaries.
Automatic style and language detection from project history.
Advanced history searching including blame, bisect, and specific string tracking (log -S).
3 GitHub stars
Parallel context gathering for status, diffs, and branch positioning.
Intelligent history rewriting with safety checks for upstream branches.

Use Cases

Splitting a large feature implementation into multiple review-ready atomic commits.
Performing deep archaeological searches to find exactly when and why a logic change occurred.
Automating the cleanup and squashing of local branch history before a pull request.

About

Key Features

Strict atomic commit enforcement based on file count and logical boundaries.
Automatic style and language detection from project history.
Advanced history searching including blame, bisect, and specific string tracking (log -S).
3 GitHub stars
Parallel context gathering for status, diffs, and branch positioning.
Intelligent history rewriting with safety checks for upstream branches.

Use Cases

Splitting a large feature implementation into multiple review-ready atomic commits.
Performing deep archaeological searches to find exactly when and why a logic change occurred.
Automating the cleanup and squashing of local branch history before a pull request.