git-smart-commit

To group changed files into logically sequenced commits, a Skill can read your modified files, understand their purpose, and execute meaningful batch commits one by one following developer workflow conventions like plans, config, core logic, tests, and docs.

The best way to commit multiple files with smart grouping is to analyze each changed file's purpose, create a commit plan that orders changes by workflow conventions, confirm the plan with the user, and execute the commits sequentially.

Automatic file grouping handles multi-file changes by reading each modified file in the branch to understand its role, clustering related files together, sequencing them according to developer workflow conventions, and executing the grouped commits sequentially.

Smart commit does not require manual staging because it discovers all changed files in the current branch automatically, reads them to determine their purpose, and presents the grouping plan to the user for confirmation before executing the commits.

You can review the commit sequence before execution because the grouping process reads all changed files, organizes them into a logically sequenced commit plan, and requires user confirmation to proceed with committing the batches one by one.

You should not use automated commit grouping when your changes are isolated to a single file or when your workflow requires custom commit ordering that deviates from standard developer conventions like plans, config, core logic, tests, and docs.