commitlisted

1. Run `git status` and `git diff` to understand what changed. 2. Run `git log --oneline -5` to match the repository's existing commit message style. 3. Draft a commit message using Conventional Commits format (see `REFERENCE.md` in this skill folder for full reference): - **First line**: `<type>[optional scope]: <description>` (imperative mood, under 72 chars) - **Types**: `feat`, `fix`, `chore`, `docs`, `refactor`, `perf`, `test`, `build`, `ci`, `revert`, `style` - **Scope** (optional): the crate or area affected, e.g. `feat(tools):`, `fix(model):` - **Breaking changes**: append `!` after type/scope, e.g. `feat!:` or add `BREAKING CHANGE:` footer - **Body** (if needed): 1-3 sentences explaining context or motivation, separated by a blank line 4. Present the message to the user for approval before committing. 5. Only commit after the user confirms.