What problem does it solve? Writing consistent, meaningful commit messages is tedious and often results in vague entries like "fix stuff" that pollute repository history. This Skill analyzes your actual diff and the repository's existing commit style to produce convention-compliant messages automatically. ## Core Features & Use Cases - Convention Detection: Samples recent repository commits and your own commit history to detect the style in use (Conventional Commits, Gitmoji, ticket-prefixed, or free-form) and matches it. - Diff-Driven Messages: Generates a subject line (≤72 characters) plus an optional body explaining why the change was made, based on the staged diff rather than a file-by-file inventory. - Safety Guardrails: Never amends, force-pushes, skips hooks, or discards changes without explicit approval, and flags potential secrets before committing. - Use Case: After finishing a feature branch with mixed staged and unstaged edits, ask for a commit and receive a properly formatted message that references the ticket number from your branch name. ## Quick Start Ask the assistant to commit my current changes with a message that follows this repository's commit style.