Can it match my existing repository commit style?

Yes. Before committing, Git Master analyzes your last 30 commits to detect your preferred language and style, whether you use Semantic Commits (feat/fix), plain text, or short summaries.

How does Git Master handle large code changes?

It enforces strict 'Commit Splitting' rules based on the number of files changed. For example, if 5 or more files are modified, it automatically breaks the work into 3 or more logical commits to ensure atomic history.

Is it safe to use for rebasing branches?

Absolutely. Git Master follows rebase safety protocols, including stashing dirty files before starting, avoiding rebases on main/master branches, and always using the --force-with-lease flag.

What is 'History Archaeology' in this context?

History Archaeology refers to the skill's ability to use advanced Git commands like bisect, blame, and grep-based logs to pinpoint exactly when a bug was introduced or who modified specific lines of code.

Git Master

Name: Git Master
Author: mikev10

bymikev10

Developer Tools

Optimizes Git workflows by enforcing atomic commits, intelligent style detection, and advanced history management.

About

The Git Master skill transforms Claude Code into a senior version control expert, ensuring your project history remains clean, logical, and professional. It specializes in decomposing complex PRs into atomic commits based on strict file-count rules, detecting and matching your repository's specific commit style (Semantic vs. Plain), and performing advanced 'history archaeology' to track down bugs. Whether you need to perform surgery on a messy rebase or automate the creation of revertible commit chains, this skill provides the guardrails and expertise needed for high-stakes repository management.

Key Features

Advanced history archaeology for finding specific code changes and regressions
Intelligent style detection based on previous 30 commits (Semantic vs. Plain)
Automatic commit splitting for large changes to maintain atomic history
Safe rebase management using --force-with-lease and stash protection
Multilingual support for commit messages in English and Korean
0 GitHub stars

Use Cases

Auditing project history to find exactly when a specific line of code was introduced or modified
Cleaning up and rewriting branch history before merging into a protected master branch
Breaking down a 10-file feature update into logical, independent commits for easier code review

About

Key Features

Advanced history archaeology for finding specific code changes and regressions
Intelligent style detection based on previous 30 commits (Semantic vs. Plain)
Automatic commit splitting for large changes to maintain atomic history
Safe rebase management using --force-with-lease and stash protection
Multilingual support for commit messages in English and Korean
0 GitHub stars

Use Cases

Auditing project history to find exactly when a specific line of code was introduced or modified
Cleaning up and rewriting branch history before merging into a protected master branch
Breaking down a 10-file feature update into logical, independent commits for easier code review