Git master
Utility: Atomic commit workflow. Analyzes changes, groups into logical commits, writes clear commit messages. Solo operation, no team needed.From its SKILL.md
npx -y skills add erkandogan/oh-my-team --skill git-masterAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 17 stars17 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, as published. Nobody here has run it
Git Master - Atomic Commit Workflow
Create clean, atomic commits from the current changes.
Protocol
Step 1: Analyze Changes
git status
git diff --stat
git diff
Understand what changed and why.
Step 2: Group Into Logical Commits
If changes span multiple concerns, group them:
- Each commit should be one logical change
- Each commit should leave the codebase in a buildable state
- Order commits so dependencies come first
Step 3: Write Commit Messages
Format:
<type>(<scope>): <description>
<body - what and why, not how>
Types: feat, fix, refactor, test, docs, chore, perf, style
Rules:
- Subject line: imperative mood, lowercase, no period, under 72 chars
- Body: explain WHY, not WHAT (the diff shows what)
- Reference issues if applicable
Step 4: Stage and Commit
For each logical group:
- Stage specific files:
git add <files> - Commit with the prepared message
- Verify:
git log --oneline -1
Step 5: Verify
- Run
git log --oneline -5to show recent commits - Confirm each commit is atomic and self-contained
Anti-Patterns
- NEVER
git add .blindly - NEVER commit .env, credentials, or secrets
- NEVER create empty commits
- NEVER amend published commits without asking
- NEVER force push without explicit permission