Skill

git-master

Analyzes git changes with status/diff, groups into logical atomic commits, stages files selectively, writes conventional messages (feat/fix/etc.), and verifies. For solo clean git history.

Git

Bash

git-workflow

npx claudepluginhub erkandogan/oh-my-team

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Create clean, atomic commits from the current changes.

SKILL.md

Similar Skills

git-commit

Organizes git workspace changes into clean, atomic commits following conventional formats. Activates after features, refactors, or explicit commit requests.

git-workflow

Commit Workflow

Guides systematic git commits: checks staging status, reviews diffs, splits changes into atomic commits, formats conventional messages. Use before PRs or when committing code.

cipherpowers

Atomic Commit

Guides atomic git commits: analyzes diffs, detects mixed concerns, groups files, stages selectively, verifies tests/builds, uses conventional messages, adds issues.

tdg

Stats

Stars15

Forks0

Last CommitApr 13, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

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 -5 to 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