Semantic Commit
Workflow
- Inspect the full diff and identify logical units of change.
- Split changes only when each resulting commit remains buildable and understandable.
- Commit in dependency order. Typical order is
refactorbeforefeat,test, orfixwhen that makes the history clearer. - Use semantic commit messages for every commit.
- Stop after local commits are created.
Guardrails
- If a safe split is unclear, prefer fewer commits.
- Never create a broken intermediate commit knowingly.
- Do not push.
- Do not rewrite existing commits.