commit-messagelisted

# Commit Message (Conventional Commits v1.0.0) <!-- routing-eval reads this line; it lives in the BODY so the always-on skill LISTING stays inside Claude Code's budget (1% of the context window) — an overflowing listing gets descriptions truncated or dropped, which strips the very keywords a match depends on. --> Trigger phrases: "commit message", "make a commit", "conventional commit", "write a commit", "git commit" Format: `type(scope): summary` + (optional blank line + body) + (optional footer). ## Type (required) - `feat` — new feature · `fix` — bug fix - `docs` — docs only · `refactor` — restructure with no behavior change - `perf` — performance · `test` — add/fix tests - `build` — build/dependency · `ci` — CI configuration - `chore` — maintenance/automated · `revert` — revert a previous commit - `style` — formatting (no logic) ### Which type? (deciding when ambiguous) - A new capability for the user? → `feat`. Fixing an existing wrong behavior? → `fix`. - Behavior the same, only the structure changed? → `refactor` (if behavior changed it's `feat`/`fix`, not refactor). - Touched only tests/docs/formatting? → `test`/`docs`/`style` (don't touch code logic). ## Scope (optional, preferred) The affected area/module: `auth`, `api`, `backend`, `db`, `frontend`, `session`, `agent`, etc. One word, consistent with the project's module name. ## Summary line - **In the project's established language** (English by default f