git-master

Executes atomic commits, non-interactive rebases, and git history searches with style detection.

1|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/UtsavBalar1231/oh-my-claudeagent --skill git-master-utsavbalar1231
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-master
Source: https://github.com/UtsavBalar1231/oh-my-claudeagent/tree/main/skills/git-master
Command: npx skills add https://github.com/UtsavBalar1231/oh-my-claudeagent --skill git-master-utsavbalar1231

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents messy, mixed-concern commits and risky history rewrites by enforcing atomic commit planning, repository style detection, and safety checks before any git mutation. ## Core Features & Use Cases - Atomic Commit Architect: Groups changed files by independently revertible concerns, pairs implementation with its tests, and matches the repository's existing commit message style (semantic, plain, short, or sentence). - Rebase Surgeon: Performs fully non-interactive rebases and squashes with a mandatory pre-rewrite safety checklist covering branch state, dirty work, push status, and recovery paths. - History Archaeologist: Finds when code was added or removed using git log -S/-G, blame, and bisect for code archaeology questions. - Use Case: After finishing a feature touching multiple modules, ask it to commit your work; it analyzes the changes, splits them into atomic commits matching your repo's style, and verifies a clean working tree. ## Quick Start Ask the agent to commit my current changes as atomic commits matching this repository's commit style.

Frequently Asked Questions about git-master

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I split changes into atomic commits with git?

Group changed files by independently revertible concerns, keeping each implementation file together with its direct tests in the same commit. Stage and commit each group separately in dependency order, then verify with git status and git log.

How to rebase git commits non-interactively in scripts?

Prefix git commands with GIT_EDITOR=: EDITOR=: GIT_SEQUENCE_EDITOR=: GIT_PAGER=cat GIT_TERMINAL_PROMPT=0 to prevent editor hangs. For squashing, use git reset --soft to the merge-base followed by a single commit, or git rebase -i --autosquash with editors disabled.

How do I find when a line of code was added in git?

Use git log -S "text" --oneline to find commits that added or removed a string, git blame -L N,N file to see who wrote a specific line, and git bisect to locate the commit that introduced a bug.

Is it safe to rebase commits that were already pushed?

Rewriting pushed history requires explicit permission and should only use git push --force-with-lease, never plain --force. On main or master branches, history rewriting should be aborted entirely.

Why should tests be committed together with implementation?

Pairing tests with their implementation keeps each commit independently revertible and verifiable. Separating them creates commits that break the build or test suite when checked out or reverted individually.