What problem does it solve? Writing clear, consistent commit messages is tedious and often skipped, leading to vague history like "update files". This Skill inspects your staged changes and drafts a standards-compliant Conventional Commits message, so your git history stays meaningful without manual effort. ## Core Features & Use Cases - Diff-Based Message Generation: Reads git diff --staged and produces a single-line type(scope): description title that reflects confirmed code facts, not guessed intent. - Multi-Language Support: Selects the description language via a priority chain (explicit request, repo config, global config, invocation language, recent commit history) while keeping Conventional Commits tokens in English. - Confirmation-First Workflow: Presents one or more candidate messages as a numbered list and only runs git commit after you pick or confirm; never pushes unless explicitly asked. - Use Case: After staging a bug fix across several files, invoke the skill to get a message like fix(auth): reject expired refresh tokens, reply "1" to commit, and optionally persist your preferred language to .agent-tools/config.jsonc. ## Quick Start Stage your changes with git add, then ask the agent to generate a commit message for my staged changes and confirm before committing.
