What problem does it solve?
Ensures git commits follow a concise Conventional Commits-style format and prevents inconsistent or unclear commit messages while avoiding accidental pushes. It reduces cognitive friction when writing commit subjects and helps maintain a readable, searchable project history.
Core Features & Use Cases
- Enforces a single-line imperative subject in the format type(scope): summary and recommends a short optional body when necessary.
- Honors file path or glob arguments to stage and commit only intended files, and prompts clarifying questions when file selection or message scope is ambiguous.
- Use Case: Quickly create a standardized commit for a bugfix touching multiple modules by providing affected file paths and a short description of the fix.
Quick Start
Create a Conventional Commits-style git commit for the current changes, stage only the modified files, and produce a concise subject and optional body describing the change.