What problem does it solve? Writing consistent, standards-compliant git commit messages is error-prone and time-consuming, especially when following the Conventional Commits specification with project-specific conventions like component scopes and AI attribution trailers. ## Core Features & Use Cases - Conventional Commit Generation: Infers the correct commit type (feat, fix, docs, chore, refactor, ci, deprecate, remove, breaking) from changelog fragments or the nature of the changes. - Message Formatting Rules: Enforces subject lines under 72 characters, imperative mood, lowercase descriptions, and BREAKING CHANGE footers. - AI Attribution: Automatically appends an Assisted-by trailer identifying the AI model and version used in the session. - Use Case: After modifying an Ansible role or module, ask the assistant to commit the changes and receive a properly formatted message like "feat: add support for custom agent port to postgresql_info module" with user confirmation before committing. ## Quick Start Ask the assistant to commit your staged changes with a conventional commit message.