What problem does it solve? Writing consistent, well-formatted git commit messages is a common friction point for developers, and inconsistent commit history makes changelogs and code archaeology harder. This Skill standardizes every commit to the conventional commit format with proper staging discipline. ## Core Features & Use Cases - Conventional Commit Formatting: Enforces the <type>: <description> single-line format with types like feat, fix, refactor, docs, style, test, chore, and perf. - Selective Staging: Stages only modified files individually, explicitly avoiding git add -A or git add . to prevent accidental commits. - Change Analysis Workflow: Runs git status, git diff, and git log to understand changes and match recent commit style before committing. - Use Case: After finishing a bug fix across three files, ask the AI to commit the changes and receive a properly formatted message like fix: resolve null pointer in job executor with only the relevant files staged. ## Quick Start Ask the AI to commit your current changes using the commit skill, and it will analyze the diff, stage the modified files, and create a conventional commit message.