Git Commit

Generate a conventional commit message and create the commit.

Quality Guidelines

Base the message only on what the diff actually shows, not assumptions:

1. Read git status and git diff --staged (or git diff if nothing is staged yet) before writing anything.
2. Check which files/modules changed before setting scope.
3. Look for removed exports, changed signatures, deleted functions to catch breaking changes.
4. If the purpose of a change is unclear, ask the user rather than guess.

Pre-commit Linting