commit-work

To split unstaged git changes into logical conventional commits, inspect the working tree and use patch staging to stage hunks selectively. This process groups related modifications into focused commits, generating descriptive messages that adhere to the Conventional Commits format for review-ready deliverables.

Patch staging enables fine-grained, hunk-by-hunk staging of code changes to keep commits focused and review-ready. By selectively staging specific segments rather than entire files, it separates feature additions, fixes, and refactors into isolated, safe-to-merge conventional commits.

The conventional commits format structures git commit messages by enforcing type and scope correctness in every commit. This discipline categorizes changes into types like features, fixes, or refactors, ensuring well-structured messages that are easy to review and safe to merge.

Yes, you can automatically generate commit boundaries for mixed code changes. The workflow analyzes the working tree and suggests logical splits across features, fixes, refactors, tests, and dependencies, providing final commit messages and staging commands for efficient reviews.

No external git tools or dependencies are required to enforce split commits. The workflow operates independently to inspect the working tree, suggest logical commit boundaries, perform patch staging, and generate conventional commit messages without additional package dependencies.