grouped-git-commits

To group related git changes, inspect the worktree to identify related modifications, stage only the intended files by topic, and commit them with a concise subject and detailed body. This ensures unrelated files are excluded from the commit.

Split unstaged worktree changes by reviewing modified files, categorizing them by topic, and selectively staging only related files for each commit. This produces multiple coherent commits, excluding unrelated work from each group.

Write multiline git commit messages by adding a concise subject line followed by a detailed body explaining the rationale behind the changes. This clarifies the context of the staged files for future review.

The best way to exclude unrelated files is to selectively stage only the specific files related to one topic at a time. This grouping prevents unrelated worktree modifications from being included in a single commit.

Yes, after grouping and committing related changes, a final summary is provided detailing what was committed, what was excluded, and how to verify the result. This confirms the worktree state and commit accuracy.

You need to group git commits by topic when your worktree contains multiple unrelated modifications. Creating grouped, multiline commits with clear subjects and bodies maintains a clean Git history and reduces ambiguity during review.