git-commit-organizer

To split messy changes into logical git commits, inventory your working tree and staged edits, then group them by intent into commit buckets before staging by file or hunk with conventional messages.

The best way to organize staged and unstaged files before a PR is to plan commits by intent—such as feature, fix, refactor, or docs—and stage changes by file or hunk to produce a cohesive history for code review.

Yes, you can stage git changes by hunk instead of by file, allowing you to isolate specific diffs within a multi-file edit and group them into separate, focused commits with clear conventional messages.

To write conventional commit messages for large feature work mixed with refactors, plan your commit buckets by intent and generate clear messages for each staged group of changes to improve history readability.

No dependencies or external tools are required to organize your git workflow, as the process applies built-in staging and diff capabilities to inventory changes and enforce a plan of commit buckets.

You should not use automated commit organization when your changes are already isolated and focused, as the inventory and commit bucket planning process is designed for multi-file edits and large feature work that should be split.