git-commit

What problem does it solve? Writing clear, consistent commit messages is tedious and often skipped, leaving repositories with vague history that is hard to review or revert. This Skill automates the full commit workflow, from inspecting changes to producing well-structured messages that match repository conventions. ## Core Features & Use Cases - Context-aware commits: Inspects git status, diffs, branch state, and recent history before committing, and stops cleanly when there is nothing to commit. - Convention detection: Follows project instructions, infers patterns from recent commit history, or falls back to conventional commit format (feat, fix, docs, refactor, and more). - Logical commit splitting: Groups changed files into separate commits when they represent distinct concerns, without splitting hunks within files. - Safety guardrails: Warns before committing directly to main or the default branch, handles detached HEAD states, and stages specific files to avoid leaking sensitive files like .env. - Use Case: After finishing a feature and an unrelated bug fix in one session, ask to commit your changes and receive two separate, properly formatted commits with messages matching your repo's style. ## Quick Start Ask the assistant to commit my current changes with a clear message following the repository's commit conventions.