Incremental Commits

When a feature touches multiple files, implement in waves. Each wave is one logical concern, one standalone commit, ordered by dependency. This creates a clean git history that reviewers can audit one commit at a time.

Related Skills: See standalone-commits for making each wave reviewable and auditable. See git for commit message conventions and PR guidelines.

Relationship To Standalone Commits

incremental-commits decides commit order. standalone-commits decides whether each commit boundary is good.

Use this skill to plan the sequence:

foundation -> implementation -> consumers -> cleanup

Then use standalone-commits to test each wave: