commit-split-workflow

To split a large multi-file diff into meaningful commits, this workflow reads repository conventions and infers logical boundaries directly from the changes. It batches modifications automatically without prompting the user for input on how to group files.

Yes, you can automate splitting git changes for code review by manually triggering this workflow. It automatically derives commit groups from the diff and repository guidance, ensuring changes are staged logically to enable easier reviews and rollbacks.

Yes, this commit-splitting workflow follows repository commit-message conventions. It reads your repository instructions to determine grouping and generates descriptive messages aligned to those specific conventions for precise version-control history.

The best way to group nested repository changes into separate commits is using a diff-analysis workflow that enforces guardrails. It reads repository instructions, handles nested repositories, and ensures changes are staged logically without asking the user how to split files.

You should avoid using an automated workflow to split changes unless you explicitly request it. This skill is manual trigger only and does not auto-run; it should only be activated when you clearly want to split changes into meaningful commits.