autommit

Format: <type>(<scope>): <description>

Default strategy: file

Strategies

• file - one commit per file for better granularity
• features - one commit per feature across files
• domain - group by business domain (auth, payments, etc.)

$ARGUMENTS

Determine grouping strategy, generate conventional commit messages. Never include co-author info.

git add <files-affected> && git commit -m "<message>"

Rules

• Imperative present tense ("add" not "added")
• ! for breaking changes: feat(api)!: change user response
• Body only when "why" isn't obvious