Commit Workflow

When to Use

• Before every commit — to enforce conventional commit format consistently
• When a diff mixes multiple logical concerns (feat + refactor + docs)
• When you want emoji-annotated commits for visual git history
• In teams that enforce Conventional Commits via CI

Prerequisites

• Changes staged or present as unstaged modifications
• Optional: pre-commit hooks configured (husky, pre-commit, or similar)

Workflow

1. Stage and Inspect

If nothing is staged, stage everything and inspect what changed: