conventional-commitlisted

# Conventional Commits Generate or review a commit message without staging files or creating a commit. ## Format ```text <type>[optional scope][!]: <imperative description> [optional body] [optional footer(s)] ``` Allowed types: `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `build`, `ci`, `chore`, and `revert`. ## Procedure 1. Inspect the available status and diff when context is provided. 2. Choose the smallest accurate type and optional scope. 3. Write a concise imperative subject with no trailing period. 4. Add body only for non-obvious reasoning, migration notes, or breaking changes. 5. Add `BREAKING CHANGE:` or issue references in the footer when needed. 6. Return the message in a paste-ready code block. ## Verification - Subject uses an allowed type and imperative mood. - Body and footer explain only information not obvious from the diff. - No staging, commit, push, or amend operation is performed.