gf-create-git-commits

To split code changes into atomic git commits, you analyze your working directory to identify distinct intentions, selectively stage hunks with git add -p, and create cohesive git commits organized by purpose for a navigable history.

Organizing a git commit history by intent involves grouping related code changes into focused commits. This ensures each commit represents a single logical modification, making the project history easier to read and review.

Using git add -p for feature development allows you to interactively select and stage specific code hunks. This guided staging process ensures only related changes are grouped before creating an atomic git commit.

Automated commit splitting works for refactoring and bug fixes by analyzing the diff to identify the specific intent of each change. It ensures clean, intentional git commits across various development tasks.

Pushing commits to a remote repository is not handled by this process. It focuses solely on analyzing local diffs, staging hunks, and creating local git commits without pushing to a remote.

You need local git tooling to create intentional commits because the process relies on local git commands like git diff to analyze changes, git add -p to stage hunks, and git commit to finalize the atomic units.