What problem does it solve? Writing consistent, well-formatted git commit messages is repetitive and often inconsistent across a project. This Skill standardizes commit creation by enforcing a Conventional Commits-style format and handling staging decisions safely. ## Core Features & Use Cases - Conventional Commits Format: Generates subjects in the form <type>(<scope>): <summary> with types like feat, fix, docs, refactor, chore, test, and perf. - Selective Staging: Honors user-provided file paths or globs to limit which changes get committed, and asks for clarification when files are ambiguous. - Scope Discovery: Optionally reviews recent commit history (git log) to reuse commonly used scopes for consistency. - Use Case: After editing several source files, ask the assistant to commit only the parser changes; it reviews git status and git diff, stages just those files, and commits with a message like fix(parser): handle empty input tokens. ## Quick Start Ask the assistant to commit the current changes, optionally naming specific files or extra instructions for the message.