git-committer-atomic

To split staged Git changes into atomic commits, analyze changes across infrastructure, core, domain, services, and features to ensure logical commit sequencing. This iteratively stages and commits logical units of work until a clean git status is reached.

Dependency-aware Git committing organizes changes into atomic commits ordered by file dependencies, such as infrastructure before core logic. You need it when implementing features that touch multiple layers and require a clean, maintainable commit history for simpler reviews and rollbacks.

The best way to organize a complex feature into logical Git commits is to group staged changes by their architectural layer. Separating configuration, core logic, and UI components into ordered commits ensures each commit addresses a single change and maintains a clean git status.

Yes, you can use atomic commits to clean up a messy git status. By iteratively staging and committing logical units of work ordered by file dependency, the process guides you efficiently from a complex mixed state to a completely clean git status.

Ordering Git commits by file dependencies instead of committing everything at once ensures each commit represents a single logical change. This dependency-aware sequencing across infrastructure, core, and features makes code reviews easier and rollbacks much simpler.

A limitation of separating staged changes into atomic Git commits is that it requires analyzing distinct architectural layers like infrastructure, core, and features. If your changes are entirely isolated to a single file or component, dependency-aware ordering provides no additional sequencing benefit.