What problem does it solve? Writing consistent, well-scoped git commit messages and grouping related changes into clean commits is tedious and error-prone, especially when sessions produce many mixed changes. ## Core Features & Use Cases - Conventional Commits formatting: Generates type(scope): subject messages with proper verbs, bodies, and footers, matching the repo's recent commit style. - Commit grouping by concern: Splits changes into separate feat, refactor, test, and docs commits, staging files by name instead of git add .. - Safety guardrails: Detects pre-commit hooks (husky, lint-staged, commitlint), warns about sensitive files like .env or private keys, and never amends or force-pushes without explicit approval. - Use Case: After refactoring a Select component and adding tests, ask the assistant to commit; it inspects git status and git diff, then produces separate commits like refactor(select): extract shared styles and test(select): cover keyboard navigation. ## Quick Start Ask the assistant to review what changed and commit the current work following the project's commit conventions.