work_git_commit-message

To generate a Conventional Commits message, the Skill analyzes your staged git diffs to classify the change type, such as feat or fix, and outputs a standardized subject and optional body. It inspects changes via git diff --staged.

The Conventional Commits format requires a type, optional scope, and a concise subject limited to 50 characters. An optional wrapped body can be appended to explain the rationale behind the staged changes.

Git diffs are classified by analyzing the nature of the staged changes. The Skill determines the appropriate Conventional Commits type—feat, fix, docs, style, refactor, test, or chore—based on what the modifications actually accomplish.

Yes, you must stage changes before generating a commit message. The Skill specifically inspects staged changes using git diff --staged to ensure the generated message accurately reflects only the modifications you have prepared for the commit.

Yes, you can define a scope within your Conventional Commits messages. The Skill enforces type and scope parameters alongside the subject length to produce consistent and standardized commit history across your git workflow.