Subject
The first line should briefly explain what changes. Scope and type help when searching the history later.
Development
Create structured commit messages from change type, scope, short description and details. The tool works completely locally in the browser and does not write a Git commit.
A good commit message briefly describes what changed and adds details, breaking changes or ticket references where needed. This tool helps with wording without forcing project rules.
0 characters in subject. Often readable: up to about 72 characters.
The first line should briefly explain what changes. Scope and type help when searching the history later.
The body is useful when the change needs explanation, covers multiple points or should document a decision.
If interfaces, data structures or behavior change incompatibly, the commit should make that clear.