Atomic Commit Skill

Atomic commits represent single, logical changes that simplify reviews and debugging. This skill analyzes your staged changes, identifies file groups by scope and type, and generates a commit sequence plan showing how to split multi-file modifications into coherent units.

File grouping for atomic commits ensures each commit addresses one concern—a feature, fix, docs update, or test. This skill examines your changes, detects dependencies between modifications, and recommends which files belong together to maintain logical cohesion.

Commit sequencing matters for reviewability and bisectability. This skill constructs a dependency graph of your changes, applies topological ordering, and produces a concrete step-by-step plan showing the order to commit files so earlier commits don't depend on later ones.

Yes. When you've made several unrelated modifications across features, fixes, and tests, this skill automates the analysis by extracting change types and scopes, grouping files logically, resolving dependencies, and delivering an interactive commit plan with scripts.

Atomic commits preserve distinct logical units in history; squashing collapses all changes into one. Atomic commits make bisecting bugs easier and code reviews clearer because each commit explains one intent, whereas squashed history loses that granularity.

Basic Git familiarity is helpful—understanding staging and branching. This skill handles the planning logic using Python and Bash tooling; you follow its recommendations to execute commits, so it bridges analysis and action without requiring deep Git internals knowledge.