Multi-Commit Workflow (Conventional)

Overview

Break a mixed-delta branch into focused conventional commits by planning the sequence, staging deliberate hunks, and reviewing each set before committing.

When to Use

• The working tree touches multiple features, refactors, or fixes that should not be lumped together.
• Preparing a pull request that must demonstrate ordered, reviewable steps.
• Sharing code where readable history matters for reviewers or downstream owners.

When NOT to Use

• Single-feature changes that are already isolated.
• Quick typo or documentation fixes that can be handled as one commit.

Quick Procedure